This Question is Not Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
0 Replies Last post: Feb 21, 2014 1:35 AM by Ben Jansen  
Ben Jansen Newbie 3 posts since
Nov 8, 2006
Currently Being Moderated

Feb 21, 2014 1:36 AM

Eliminate extra builds due to "finish build" trigger

Hello,

 

I would like to know whether it is possible to reduce the number of extraneous builds that the "finish build" trigger can cause.

 

For example, say I have build configurations A, B, and C. All have VCS triggers. B has a finish build trigger on A. C has a finish build trigger on A and B. When a new build of A occurs, B and C will be queued. If B completes its build first, another C build is queued. The second C build is unnecessary.

 

You can imagine that the number of unnecessary builds increases as you increase the number of components you are building.

 

Is it possible to reduce the number of extraneous builds in this scenario, without removing the build triggers? If it's not currently possible, could TeamCity include this feature in the future? I think that if the finish build trigger checked whether a build is already queued before adding a new one, the situation would be greatly improved. There may be other options, like some sort of quiet period.

 

Thanks.

More Like This

  • Retrieving data ...