Prevent parallel builds of same build definition.
Hi,
To utilize our build environment optimal, we have several build engines all supporting all our build definitions.
This setup enables two users to request build of the same build definition at the same time.
The second user are warned:
"A 'my build definition' build is already in progress. Are you sure you want to request another one?"
But if he press ‘yes’, they will run in parallel.
I want to prevent this - but have not found a way.
Best solution would be if RTC could queue the second build.
It is not a solution to dedicate only one build engine for each build definition.
|
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Sep 30 '15, 9:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Every build request is put in the build definition's build queue. So the builds are queued anyway. The build engines poll in the queues and once they are done look for the next request.
You have an option to throttle personal builds and "public" builds using https://rsjazz.wordpress.com/2013/11/22/seperating-personal-from-other-builds/ this would allow you to prioritize public builds on the cost of developers waiting longer. If you want more, the only option that I see today is to come up with our own server request build advisor. This would have to be custom built by you and could check for builds under way and if you want to allow the request to go through. 
If you want to do such a thing, start here: https://rsjazz.wordpress.com/2015/09/30/learning-to-fly-getting-started-with-the-rtc-java-apis/ |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.