Continuous Integration
CI Labels Guide
[ci/run-xxx ...]
: Run additional steps in the PR workflow indicated byci/run-xxx
in your PR.ci/pr/run-selected
+[ci/run-xxx ...]
: Only run selected steps indicated byci/run-xxx
in your DRAFT PR.ci/main-cron/run-all
: Run fullmain-cron
workflow for your PR.ci/main-cron/run-selected
+[ci/run-xxx …]
: Run specific steps indicated byci/run-xxx
from themain-cron
workflow, in your PR. Can use to verify somemain-cron
fix works as expected.- To reference
[ci/run-xxx ...]
labels, you may look at steps frompull-request.yml
andmain-cron.yml
.
Example
https://github.com/risingwavelabs/risingwave/pull/17197
To run e2e-test
and e2e-source-test
for main-cron
in your pull request:
- Add
ci/run-e2e-test
. - Add
ci/run-e2e-source-tests
. - Add
ci/main-cron/run-selected
to skip all other steps which were not selected withci/run-xxx
.
Main Cron Bisect Guide
- Create a new build via buildkite
- Add the following environment variables:
GOOD_COMMIT
: The good commit hash.BAD_COMMIT
: The bad commit hash.BISECT_BRANCH
: The branch name where the bisect will be performed.CI_STEPS
: TheCI_STEPS
to run during the bisect. Separate multiple steps with a comma.- You can check the labels for this in main-cron.yml, under the conditions for each step.
Example you can try on buildkite:
- Environment variables:
GOOD_COMMIT=29791ddf16fdf2c2e83ad3a58215f434e610f89a BAD_COMMIT=7f36bf17c1d19a1e6b2cdb90491d3c08ae8b0004 BISECT_BRANCH=kwannoel/test-bisect CI_STEPS="test-bisect,disable-build"