Hi, Thank you for your answer.
I'm afraid the publishers section is too late: I need to unmount the database before I can pack it together with the binaries into the installer: 1. mount db 2. compile app 3. run tests 4. generate PNG pictures from SVGs 5. unmount db 6. generate installer By using the publishers section, I would need to move step 6 (installer generation) to the publishers section too, which means I would not have logs for it. On Fri, Nov 25, 2011 at 7:14 PM, Rolando Valdivia <[email protected]> wrote: > You can use the publishers section for this purpouse. The publishers > run whether the build passes or fails, and you can call any task in this > configuration block. > Regards, > Rolando > > 2011/11/25 Pau Garcia i Quiles <[email protected]> >> >> Hi, >> >> Thank you but that is not what I want. >> >> Say we have these tasks: >> >> 1. mount db >> 2. compile app >> 3. run tests >> 4. generate PNG pictures from SVGs >> 5. unmount db >> 6. generate installer >> >> With a sequential task, I would wrap steps 1-4: >> >> <sequential continueOnFailure="true"> >> 1. mount db >> 2. compile app >> 3. run tests >> 4. generate PNG pictures from SVGs >> 5. unmount db >> </sequential> >> 6. generate installer >> >> I don't care about step 3, but by making this sequential, I may end up >> with an installer with corrupt images because something failed in step >> 4 >> >> I was hoping for a "go to this task in case something fails" task. >> >> >> >> On Fri, Nov 25, 2011 at 6:10 PM, Matthias Napalowski >> <[email protected]> wrote: >> > It is possible.. With a sequential task >> > >> > http://build.nauck-it.de/doc/CCNET/Sequential%20Task.html >> > >> > Dont know who owns this build server.. Just found it with google... >> > >> > Regards >> > >> > >> > >> > Am 25.11.2011 um 16:25 schrieb Pau Garcia i Quiles >> > <[email protected]>: >> > >> >> Hi, >> >> >> >> One of the steps of the build of my project requires updating a >> >> database. >> >> >> >> I have a small utility which is run as the first task and mounts the >> >> database. That's the "setup" part. >> >> >> >> I am also invoking the utility as the last task to dismount the >> >> database. That's the "teardown" part. >> >> >> >> Problem is when the build fails for some reason, CC.NET never executes >> >> the teardown part, therefore the database connection remains open, >> >> which causes trouble. >> >> >> >> Is it possible to force-run some tasks, even after an exception? >> >> Something like: >> >> >> >> try { >> >> All the steps in the build process go here >> >> } finally { >> >> Teardown >> >> } >> >> >> >> Thank you >> >> >> >> -- >> >> Pau Garcia i Quiles >> >> http://www.elpauer.org >> >> (Due to my workload, I may need 10 days to answer) >> > >> >> >> >> -- >> Pau Garcia i Quiles >> http://www.elpauer.org >> (Due to my workload, I may need 10 days to answer) > > -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
