mz-debug-ci: add reference for triggering and scoping CI runs - #37883
Open
bosconi wants to merge 1 commit into
Open
mz-debug-ci: add reference for triggering and scoping CI runs#37883bosconi wants to merge 1 commit into
bosconi wants to merge 1 commit into
Conversation
Document three recipes that came up while investigating a PR's CI coverage: - Manually triggering a nightly on main (the pipeline's `branch_configuration: v*` filter blocks API builds unless `--ignore-branch-filters` is passed). - Scoping a build to specific steps via `CI_TEST_SELECTION` / `CI_TEST_IDS`, and why selection is step-granular (no single-`.td`-file selection in CI). - How testdrive coverage differs across the test, nightly, and release-qualification pipelines. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "Reference: triggering and scoping CI runs" section to the mz-debug-ci skill, capturing three things that came up while investigating a PR's CI coverage but weren't documented:
main. Thenightlypipeline'sbranch_configuration: v*blocks API builds on non-v*branches with422 Branches have been disabled; pass--ignore-branch-filters(-i). Scheduled runs bypass the filter.CI_TEST_SELECTION(step ids) /CI_TEST_IDS(indices), read byci/mkpipeline.py. Selection is step-granular; there is no single-.td-file selection in CI (run those locally).test(1 default config, sharded x20),nightly(9 mzcompose config variants),release-qualification(1 cloudtest/K8s pass, ~24h build).Pure docs addition to the skill; no behavior change.
Files
.agents/skills/mz-debug-ci/SKILL.md(+49 lines)Test plan
ci/mkpipeline.py,ci/nightly/pipeline.template.yml,ci/release-qualification/pipeline.template.yml, and live Buildkite builds.🤖 Generated with Claude Code