Skip to content

ci: avoid triggered-by-schedule and triggered-by-merge builds cancelling each other - #23716

Merged
rapids-bot[bot] merged 2 commits into
NVIDIA:mainfrom
jameslamb:nightly-builds
Aug 19, 2026
Merged

ci: avoid triggered-by-schedule and triggered-by-merge builds cancelling each other#23716
rapids-bot[bot] merged 2 commits into
NVIDIA:mainfrom
jameslamb:nightly-builds

Conversation

@jameslamb

Copy link
Copy Markdown
Member

Contributes to rapidsai/build-planning#278

Today, merging a PR while the nightly build is in progress can lead to it being cancelled.
This updates CI configurations to prevent that.

@jameslamb jameslamb changed the title WIP: ci: avoid triggered-by-schedule and triggered-by-merge builds cancelling each other ci: avoid triggered-by-schedule and triggered-by-merge builds cancelling each other Aug 19, 2026
@jameslamb jameslamb added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Aug 19, 2026
Comment thread .github/workflows/build.yaml Outdated
@jameslamb
jameslamb marked this pull request as ready for review August 19, 2026 01:58
@jameslamb
jameslamb requested a review from a team as a code owner August 19, 2026 01:58
@jameslamb
jameslamb requested a review from gforsyth August 19, 2026 01:58
@NVIDIA NVIDIA deleted a comment from copy-pr-bot Bot Aug 19, 2026
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: a184c910-5c35-4bb0-81ef-287559d5a2ef

📥 Commits

Reviewing files that changed from the base of the PR and between 1d3dafe and f57e6d0.

📒 Files selected for processing (1)
  • .github/workflows/build.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 9 remain after this review.


📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Improved workflow run management by separating concurrent builds according to their selected build type.

Walkthrough

The build workflow now separates concurrency groups by build_type. Unspecified dispatches use branch as the default value.

Changes

Build workflow concurrency

Layer / File(s) Summary
Include build type in concurrency key
.github/workflows/build.yaml
The concurrency group key now includes the workflow-dispatch build_type input and defaults to branch when unspecified.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to f57e6

This localized CI configuration change prevents scheduled and merge-triggered builds from cancelling each other, with no actionable merge-blocking risk remaining after normal checks and review.

Suggested reviewers: bdice, jolorunyomi, paul-aiyedun

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly describes the CI concurrency change that prevents scheduled and merge-triggered builds from cancelling each other.
Description check ✅ Passed The description directly explains the CI cancellation problem and the purpose of the configuration change.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@jameslamb

Copy link
Copy Markdown
Member Author

/merge

@rapids-bot
rapids-bot Bot merged commit 70bf0bc into NVIDIA:main Aug 19, 2026
91 checks passed
@jameslamb
jameslamb deleted the nightly-builds branch August 19, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improvement / enhancement to an existing function non-breaking Non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants