Hello -- I have 3 jobs in a stream relationship -- let's call them A, B & C. Only 1 can run at a time.
So I checked the configuration "Block build when upstream project is build" and "Block build when downstream project is building". And everything worked as expected. This was on Jenkins build 1.530. Recently upgraded to 1.611 (for other features) and now I find if 2 get queued while the third is running, nothing will start. (e.g., C running, A & B depend on different SVN areas. If changes come in both areas, A & B get queued. Once C finishes, neither A or B will start). It turns out that despite the text about, the "help" on those checkboxes say "building or queued". So that's why neither A or B will start. Working as designed (and apparently behaviour in 1.530 was a bug?) While I suppose there's a use case for "building or queued", my need is solely for "building". I tried the "Build Blocker" plugin, but has the same operational behaviour as the checkboxes. My initial search for plugins didn't turn up what I needed (but perhaps my search parameters are wrong.) So is there a plugin or core functionality that will only block a job from starting if another in the steam is building? (In my scenario, I don't care if A or B starts when both queued. Ideally A but if B runs, will run C and when that finishes will run A, which will start B and then C again. So doesn't really matter. What I need to get out of is nothing running and jobs staying queued forever). Thanks, Doug Blondin -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6498d745-f3c3-43a3-9eaa-a94b70cb6820%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
