What I ended up doing was breaking out some of the more complex sub-steps into NAnt scripts. This being one of them. Then coordinating the NAnt internals with the build configuration. So I have a trigger that's interval if mod exists, and one that's scheduled daily forced. I coordinate this NAnt script with the daily to do a little extra "cleaning" work which will help us verify the robustness and integrity of the build. Just in general, I am also finding that using NAnt in this manner is a VERY EFFECTIVE, VERY POWERFUL way of supporting project configurations, without having to be in the guys of the main project area all the time. Call it, decoupling the project steps from the project config itself. Very nice way of handling it.
On Wed, Aug 17, 2011 at 8:03 AM, Michael Powell <[email protected]>wrote: > I think I see what you're saying. So this "project_include" block let's say > defines everything but for the triggers. Then I can setup my different > projects / triggers and include that block. Something along those lines. > Thank you... > > > On Wed, Aug 17, 2011 at 1:49 AM, Benjamin Baumann > <[email protected]>wrote: > >> What about creating a code block (with cb:define) including all the >> project's code except the trigger? You still use two projects block but the >> codes inside are two instance of the same code. >> >> >> 2011/8/17 Michael Powell <[email protected]> >> >>> I should mention, in my cursory analysis of the CC.NET domain, the best >>> I can come up with is I will need to specify two separate project code >>> blocks for the same core project spec, each with its own trigger block. Kind >>> of defeats the purpose of the project code block if you ask me, but >>> whatever... >>> >>> >>> On Tue, Aug 16, 2011 at 4:07 PM, Michael Powell <[email protected]>wrote: >>> >>>> No, it's almost a multi-trigger/or situation but not quite. >>>> >>>> For the same project code block, I want to expand one instance of the >>>> same project to run nightly force builds. I want to then expand a second >>>> instance of the same code block to run at intervals if modifications exist. >>>> >>>> The closest approximation I have been able to come up with is along the >>>> lines what you suggested here. But that would get us both projects running >>>> if either triggers was the case, which is not what I want. >>>> >>>> >>>> On Tue, Aug 16, 2011 at 1:55 AM, Benjamin Baumann < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> If I understood you well, you are searching for a multi trigger ( >>>>> http://mjpento.dyndns.org/blogs/?p=197 or >>>>> http://build.sharpdevelop.net/ccnet/doc/CCNET/Multiple%20Trigger.html) >>>>> with an or operator between a scheduled and an interval trigger. >>>>> >>>>> Cheers, >>>>> Benjamin >>>>> >>>>> >>>>> 2011/8/16 Michael <[email protected]> >>>>> >>>>>> Is it possible to setup a Triggers block with Conditional-based >>>>>> timers? For instance, for the same Project block, I would like to fire >>>>>> off a Daily build that runs once a day and only once a day; Scheduled >>>>>> Trigger, if you will. Then turn around and specify a Developer build >>>>>> in the same Project block, but have it run at intervals, call it >>>>>> Interval Trigger, if you will. Is something like this possible? The >>>>>> only other recourse we seem to have is to repeat the same Project code >>>>>> block the only difference between the two (for the most part) is the >>>>>> Trigger block. >>>>>> >>>>>> Thank you... >>>>>> >>>>>> Regards, >>>>>> >>>>>> Michael >>>>>> >>>>> >>>>> >>>> >>> >> >
