[ http://jira.codehaus.org/browse/CONTINUUM-682?page=comments#action_64955 ]
Christian Gruber commented on CONTINUUM-682: -------------------------------------------- Workaround is to set a schedule not in the past, but vastly in the future. (I use 2061, 'cause I like Arthur C. Clarke). Anyway, such a scheduled build is unlikely to ever be executed, and it can be re-targeted at another schedule once this is implemented. For myself, I have several build definitions hitting against "never run" schedules. Particularly, I made the DEFAULT_SCHEDULE be the never run one, so that by default I get null behaviour by adding a new project, which is what I need for my own situation. > Builds that are only On Demand, not scheduled > --------------------------------------------- > > Key: CONTINUUM-682 > URL: http://jira.codehaus.org/browse/CONTINUUM-682 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.3 > Reporter: David Eric Pugh > > > I would like to be able to have a build that is purely on demand, without > editing build targets. For example, I want to run a build that deploys my > applciation to test, but I dont' want it scheduled. Or runs our Selenium > tests, but again, only on demand. Currently you must pick a schedule. I > tried setting a schedule for 1970, so it would never run automatically, but > Continuum prevented me by saying it would never run. While that was nice, i > would rather have a warning then be prevented! -- 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
