-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest: add roachstress-ci.sh #70435
Conversation
This is a handy way to trigger a CI job that stresses roachtests. For example: > BRANCH=release-21.2 SHA=99a4816fc272228a63df20dae3cc41d235e705f3 > TEST=yscb/F/nodes=3/cpu=32 COUNT=10 > ./pkg/cmd/roachtest/roachstress-ci.sh Release note: None
Testing: (Edit: this looks like it worked, except I had a typo in "ycsb" so it didn't actually work) https://teamcity.cockroachdb.com/viewLog.html?buildId=3469592&buildTypeId=Cockroach_Nightlies_RoachtestStress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
PS: looks like you committed the |
Also, shouldn't these scripts be under |
exit 1 | ||
fi | ||
|
||
if [ ! -v TEAMCITY_TOKEN ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and below we test if some variables are set. For variables where we require a value, we may want to explicitly check that they are non-empty, since a variable can be set but empty.
I'll close it but I linked it into #69289 so it can be picked up again from there. |
This is a handy way to trigger a CI job that stresses roachtests.
For example:
Resolves #69289.
Release note: None