Skip to content

ci: add nightly load testing on master#9693

Merged
alvin-huang merged 1 commit into
masterfrom
ci/nightly-load-test
Feb 3, 2021
Merged

ci: add nightly load testing on master#9693
alvin-huang merged 1 commit into
masterfrom
ci/nightly-load-test

Conversation

@alvin-huang
Copy link
Copy Markdown
Contributor

This PR triggers a nightly load test job on the master branch. It will spin up the load test cluster using the dev build from the latest commit.

I had to modify the load-test job slightly to use a local variable that is set to pipeline.parameters.commit if set (when we apply the pr/load-test label and trigger the job through the API against a PR commit) and git rev-parse HEAD if not (in nightly tests).

@alvin-huang alvin-huang requested review from a team and schristoff February 2, 2021 22:29
@github-actions github-actions Bot added the type/ci Relating to continuous integration (CI) tooling for testing or releases label Feb 2, 2021
@vercel vercel Bot temporarily deployed to Preview – consul-ui-staging February 2, 2021 22:30 Inactive
@vercel vercel Bot temporarily deployed to Preview – consul February 2, 2021 22:30 Inactive
@hashicorp-ci
Copy link
Copy Markdown
Contributor

🤔 Double check that this PR does not require a changelog entry in the .changelog directory. Reference

@hashicorp hashicorp deleted a comment from hashicorp-ci Feb 2, 2021
@alvin-huang alvin-huang merged commit 0d1301c into master Feb 3, 2021
@alvin-huang alvin-huang deleted the ci/nightly-load-test branch February 3, 2021 20:59
@hashicorp-ci
Copy link
Copy Markdown
Contributor

🍒 If backport labels were added before merging, cherry-picking will start automatically.

To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/322545.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/ci Relating to continuous integration (CI) tooling for testing or releases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants