Hi
what do you mean with 'the deployment project thinking it is running forever' --> you launch the new exe from CCNet itself? I would expect a timeout in that case, (unless you configered it to have a timeout of a few years) you should launch the new exe with in a 'fire and forget' manner: do this by launching a batch file from the deployment app, iso your exe. this batch file contains the following start <your exe> This should start your program, and return to ccnet. with kind regards Ruben Willems with kind regards Ruben Willems On Thu, Nov 20, 2008 at 10:47 PM, kramed <[EMAIL PROTECTED]> wrote: > > Ok doing this works but there still remains the deployment project > thinking it is running forever. Is this just something we have to live > with? > > On Nov 20, 2:28 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote: > > Hi > > > > you can use 2 ccnet projects : > > 1) for the build and test of you console app > > 2) for the 'deploymenyt' of your app > > > > project 2 can watch project 1 with a project trigger : > > http://confluence.public.thoughtworks.org/display/CCNET/Project+Trigger > > > > now when project 2 starts, the first task is to kill the running exe, > > copy the new version, and start it again > > > > you can put all this logic also in 1 project, but you have to > > built in a safe feature, only kill and start the process again on a > > succesfull build > > > > Hope this helps > > > > with kind regards > > Ruben Willems > > > > On Thu, Nov 20, 2008 at 4:42 AM, kramed <[EMAIL PROTECTED]> wrote: > > > > > The app that I am using CC to build is also a server process that runs > > > on the same machine. The app is a console program (web service) that > > > should run 24/7. I have CC setup to kill my app before it builds but I > > > am having an issue figuring out how to best launch the app after > > > build. I have tried a simple batch file using <exec> but CC believes > > > the build is incomplete as the exec does not return any codes as the > > > app is still running as it should be. Can anyone recommend a way > > > around this? How do I let CC finish its process but also launch the > > > app as soon as a new build is successful? This is the first time I > > > have set anything like this up before so forgive me if its a simple > > > command. >
