Skip to content

[CI] Move nightlies for maintenance/active releases into single workflows. - #23419

Open
hageboeck wants to merge 2 commits into
root-project:masterfrom
hageboeck:olderBranchNightlies
Open

hageboeck wants to merge 2 commits into
root-project:masterfrom
hageboeck:olderBranchNightlies

Conversation

@hageboeck

@hageboeck hageboeck commented Sep 18, 2026

Copy link
Copy Markdown
Member

ROOT 6.26 to 6.30 are in maintenance support level, so they run only every second night. Their workflows are barely visible for the shifter, so this PR puts them all in the same workflow.
The same is done for the active releases 6.36 and 6.40.

A while ago this was demonstrated for the doxygen build, which looks like this now (instead of being scattered over four workflows):
image

@hageboeck hageboeck self-assigned this Sep 18, 2026
@hageboeck
hageboeck requested a review from dpiparo as a code owner September 18, 2026 13:27
@hageboeck hageboeck added the skip ci Skip the full builds on the actions runners label Sep 18, 2026
@github-actions

github-actions Bot commented Sep 18, 2026

Copy link
Copy Markdown

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 23f987f.

♻️ This comment has been updated with latest results.

ROOT 6.26 to 6.30 are in maintenance support level, so they run only
every second night. Their workflows are barely visible for the shifter,
so put them all in the same workflow.
ROOT 6.32 and 6.36 are in active support level. They can't be pinned to
the top of the workflow list because the slots are occupied by other
builds.
Here, all active release jobs are placed into one workflow file.
@hageboeck hageboeck changed the title [CI] Move nightlies for maintenance releases into a single workflow. [CI] Move nightlies for maintenance/active releases into single workflows. Sep 18, 2026
@dpiparo

dpiparo commented Sep 19, 2026

Copy link
Copy Markdown
Member

Thanks for these changes. Just a small note, not really important: the support for 6.26 officially ended, but given the cost of maintaining the branch alive, some builds are still ran. I think the same will happen to 6.28 at the end of the year as per Release and Support Plan. It's not too urgent to decide right now when to stop the builds, and all the above does not make this PR any less valuable.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip ci Skip the full builds on the actions runners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants