Skip to content

Set job to "unstable" if skipping entire (non-empty) queue #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Set job to "unstable" if skipping entire (non-empty) queue #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion Jenkinsfile.trigger
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,12 @@ node {
jobName += 'queue: 0'
breakEarly = true
}
if (skips > 0 ) {
if (skips > 0) {
jobName += ' skip: ' + skips
if (breakEarly) {
// if we're skipping some builds but the effective queue is empty, we want to set the job as "unstable" instead of successful (so we know there's still *something* that needs to build but it isn't being built right now)
currentBuild.result = 'UNSTABLE'
}
// queue to build might be empty, be we still need to record these skipped builds
breakEarly = false
}
Expand Down