Re: Forcing failed builds
Lincoln Peters <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jul 5, 2010 at 6:45 AM, Mihelcsik Ádám <[email protected]> wrote: > Hello! > > We are running CC (2.7) on 5 different project on the same Trunk code, but > using different code branches for the different projects. > Sometimes the build fails on 1 branch, but it is okay on the others. > After this happens, then someone commits the correction (to the trunk, and > all the projects have this SVN url in modification set), so CC start all the > projects. > Our problem is that, CC does not start the failed project first. I think it > is random how it starts the projects. > > Is there any option to set "run the failed builds first"? Or how can I > configure the projectqueue? It's not random, although it may seem that way. CruiseControl will add a project to the build queue either when the scheduled time comes, or when the specified number of minutes has passed since the last build. It then executes the builds in FIFO order. This does mean that the build order can seem to be random, especially if the scheduling is more complex than all simple intervals or all time-based. I don't think there's a way to set priority for builds, but you might be able to get the same result by using a "veto" rule that prevents one project from building if another project fails. However, if you need the other projects to still be able to build if one fails, this may not be an acceptable solution. -- Lincoln Peters <[email protected]> ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first