[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_66245 ]
toli kuznets commented on CONTINUUM-509: ---------------------------------------- Having an ability to always execute a scheduled build is very useful, regardless of whether or not there were any code changes checked in. This is a great way to uncover race conditions - the more often the tests run, the safer you feel. Isn't that the whole idea of unit testing? the hourly/nightly builds are always running and always testing, even if you are out on vacation. So I strongly believe that being able to always have the build run even if there were no changes is a core part of Continuum functionality > Ability to process scheduled builds the same as forced builds. > -------------------------------------------------------------- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.2 > Reporter: Shinobu Kawai > Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
