-
Notifications
You must be signed in to change notification settings - Fork 13
CICD User Guide
The PR template includes checkboxes to exclude specific CI jobs. These can be used to skip certain long-running tests (e.g., regression tests) that aren't related to the feature under development. Just x the boxes as needed.
The regression suite includes additional per-feature checkboxes, use these to include only a subset of regression tests.
Note: For compatibility reasons, all regression jobs will run if no regression checkboxes are checked.
Below are some example scenarios where the pipeline may need to be rerun.
Note: In no case is it necessary to push an empty commit.
For multiple, use the Re-run failed jobs option. For just one, use the 🔄 next to the failed job in the left sidebar. Stateless and integration fails that passed on rerun will be removed from the HTML report.
Screencast.from.2026-01-23.02.51.18.PM.webm
If you changed the checkboxes in the PR description, those changes can be picked up in a rerun, so long as the config job is rerun.
Note: There is some delay between editing a PR description and when the config job can see the changes, wait a minute after editing before triggering the rerun.
Use the Re-run all jobs option. Alternatively, if the PR has fallen behind, consider the Update branch button, the resulting merge will trigger the pipeline.
Screencast.from.2026-01-23.02.54.17.PM.webm
Editing the PR description to run all jobs may be more work than is required, it is possible to manually run CI against a PR branch. By default, successful builds and passing tests may get skipped. The Run without cache option is available to disable this.