Hi Russ, You need to use the Project Trigger documented here:
http://confluence.public.thoughtworks.org/display/CCNET/Project+Trigger Basically, create a whole new project that describes the full rebuild process and use the Project Trigger described in the above link with <triggerStatus>Failure</triggerStatus> Regards, Shaun On 16 Feb, 15:08, "[email protected]" <[email protected]> wrote: > Shaun, > > Im researching FullRebuildOnFail to use because my upgrade did not > solve my lastchangelabeller problems. Im STILL failing when ccnet gets > an 'unknown' from lastbuildlabeller, or when the 'trasaction # is out > of range'. The only solution I 'and Helmut' have found, is to build > again. Id like to set a trigger so that CCNET knows that if it fails > it needs to build again. > I cant find any reference to fullrebuildonfail in the > documentation, can you point me in the direction of the code snippet > for that trigger, and would I use that trigger instead of the > 'forcebuild' trigger? > > thanks, > -Russ > > On Feb 16, 6:55 am, CinnamonDonkey <[email protected]> > wrote: > > > Hi Ruben, > > > http://jira.public.thoughtworks.org/browse/CCNET-1367 > > > Perhaps, a better description of what I am doing would help with > > picturing the scenario. > > > During the development of my new project in the ccnet.config. I know > > that I will be changing the config file on a regular basis this is > > because I have many complex tasks written in Python that all need to > > be functioning correctly or I may need to add new script parameters to > > cater for new cases. > > > By default projects are always initialised in the 'started' state. > > This is a problem because I have a "FullRebuildOnFail" Project Trigger > > that gets kicked into action when the quicker main project that I am > > working on fails. Unfortunately the project in development is failing > > on a regular basis at the moment, or classed as a 'Failed' if I have > > to 'Abort' it (I'm trying to coordinate tools across multiple > > machines). > > > As a result, if I forget to stop the "FullRebuildOnFail" project > > before starting the project in development it gets triggered - which > > is a pain. > > > The only solution currently is to cut out this project from the > > script. It would be much nicer is I could set an > > startupStatus="Stopped" in the config or better yet have a new status > > "Unavailable". Whilst "Stopped" would initialise in the stopped state > > but the "Start" button would still be available on the web dash. The > > "Unavailable" State would list the project in a stopped state but hide > > the "start" button. > > > The idea is specifically that I do not want these projects to trigger > > whilst I am developing a new project they depend on. Once I have > > finished development I can then revert them back to start as normal. > > > Hope this helps, > > Shaun > > (CCNET V1.4.2)
