That would be one way of skinning the cat but not quite what I was looking for. I would really like to be able to fire off the documentation at any time and not have it stop any other projects from being built. I realize that they may be slowed down but they would still go through at a reasonable time. Stopping integration while the documentation gets built will not work for us. I also figure that I will need to have a test in the documentation task to test and see if the documentation is already started. Any other ideas on how to fire this off? Maybe start another CCNET server? That would seem a little more complex than it needs to be.
I also thought about just moving it to the bottom of a queque, but even then it would eventually fire off and then delay all other builds until it was done. We have about 40 different active projects right now in our ccnet.config. Thanks again, KMF On Feb 6, 3:33 pm, Ruben Willems <[email protected]> wrote: > Hi > > you can use a second ccnet project or a second trigger, > and when this trigger/project is fired, you run the documentation. > > so you do not run the create documentation, only in the nightly build. > > or you can look at the process class in .NEt > this can also be of help > > with kind regards > Ruben Willems > > On Fri, Feb 6, 2009 at 9:28 PM, KMF <[email protected]> wrote: > > > I need to be able to fire off a executable or batch file and not wait > > around for the result. When I compile my program I would like to also > > rebuild the source code documentation. The thing is that building the > > app takes about 30 seconds and rebuilding the source code > > documentation takes 40 minutes. I would like to spawn this > > documentation off and not have it interfear with the rest of my ccnet > > process. > > > I cannot seem to find the answer in the docs or googling the groups. > > I am sure this has been solved before so I will just ask you all. > > > Thanks in advance, > > KMF
