[CI] Publish artifacts when a branch finishes#2362
Open
leo-automation wants to merge 2 commits intodevelopfrom
Open
[CI] Publish artifacts when a branch finishes#2362leo-automation wants to merge 2 commits intodevelopfrom
leo-automation wants to merge 2 commits intodevelopfrom
Conversation
leo-automation
changed the title
umangyadav
approved these changes
May 5, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Jenkins CI pipeline to publish tuning database artifacts (*.tsv) as soon as each matrix branch finishes (and best-effort on failure), so artifacts become visible without waiting for all parallel branches to complete.
Changes:
- Archive
build/*.tsvimmediately after stashing in the “Stash Databases” stage. - Add a best-effort
archiveArtifactscall in thefinallyblock to publish partial DBs even if the branch fails/aborts.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Per-arch tuning DBs are currently only published at the end of the weekly Tuning matrix, after every parallel branch (gfx908/gfx90a/gfx942/gfx950/gfx1100/gfx1201) finishes. A single slow or failing branch hides the DBs that the rest already produced.
This adds an archiveArtifacts 'build/*.tsv' in the matrix row's finally block, so each branch publishes its own DBs as soon as it finishes independent if it is success or failure