Forced builds only in CCNET?
I’ve been trying to setup CruiseControl.Net to only build a project when the ‘Force’ button is clicked.
After scouring the internet for the proper setup to do this, I don’t see any trigger that allows me to do this. I’ve setup a ScheduleTrigger that only allows builds at 9:00:00 each day, so right now there’s at least one build a day, but it’s just wasteful. I only want a build when someone specifically needs one, not at random times.
Does anyone know if this setup can exist in CCNET?
Slava Imeshev said,
Wrote on August 3, 2008 @ 12:08 am
If you were looking for a solution out side of CCNET, you could look at Parabuild. A manual build is a stock option in it.
Scott said,
Wrote on August 3, 2008 @ 3:40 am
Depends on which version of CC.NET you are using. There used to a ForceBuildScheduleTrigger which would do what you want. In the latest builds, this is replaced by the ScheduleTrigger with a buildCondition=”ForceBuild”.
http://confluence.public.thoughtworks.org/display/CCNET/Schedule Trigger for more information.
ben said,
Wrote on August 3, 2008 @ 8:59 am
@Scott, the buildCondition=”ForceBuild” looks like it means that a build will happen whether or not there are modifications in source control. I don’t it’s related to the ‘Force’ button.
I’m currently using a FilterTrigger with startTime=8:59:00 and endTime=9:00:00. This means there is one millisecond in which a build could happen during the day, if there are modifications.
Ideally, I’d like to set the FilterTrigger with startTime=9:00:00 and endTime=9:00:00 such that there is never a time when a build can happen.
@Slava, I’d really prefer to not throw another software package in the mix at this point.
Scott said,
Wrote on August 3, 2008 @ 12:02 pm
Sorry, you’re right about the buildCondition scenario. I checked some more and what you want is to specify an empty trigger section: .
Scott said,
Wrote on August 3, 2008 @ 12:03 pm
hmmm…the XML for my last comment didn’t come through…it should have been [triggers/] where the “[” are “” respectively.
Scott said,
Wrote on August 3, 2008 @ 12:04 pm
arrrggg…one last time, it should be: <triggers/>
ben said,
Wrote on August 3, 2008 @ 3:28 pm
oh man, how did I miss that? it’s right in the documentation on the triggers page, thanks!