Skip to content
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

Jump to bottom

Now: No sub-jobs #916

Closed
refack opened this issue Oct 13, 2017 · 2 comments
Closed

Now: No sub-jobs #916

refack opened this issue Oct 13, 2017 · 2 comments
Labels
incident

Comments

@refack
Copy link
Contributor

refack commented Oct 13, 2017

Probably as a result of updating to Jenkins 2.73.2 (done around 2017-10-13 01:00 UTC - #775 (comment))

Reported by @Trott on IRC - http://logs.libuv.org/node-build/2017-10-13#05:15:21.326

Resolved by @joaocgreis around 2017-10-13 17:00 UTC http://logs.libuv.org/node-build/2017-10-13#14:18:41.955
@refack refack closed this as completed Oct 13, 2017
This was referenced Oct 13, 2017
Closed
Closed
@joaocgreis
Copy link
Member

This happened because the Jenkins update fixed #265 (note this has been around for so long because subsequent plugin versions also had issues, let's hope this one really fixes it).

So, we now have to disable all the checkboxes that say "Build only if SCM changes", under advanced, in multi-job jobs. This is still an issue on many jobs in Jenkins. @nodejs/build I plan to go over and fix it as soon as I can, meanwhile please do it for any jobs you notice failing.

@joaocgreis joaocgreis reopened this Oct 14, 2017
@joaocgreis
Copy link
Member

All switches flipped. Should be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
incident
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@refack @joaocgreis