[Anthill] Run a deploy task on SUCCESS builds?

[Tim Colson]

> As to the deploy task. There are ways to register custom code 
> to listen for successful or failed builds, but that level of 
> complexity probably isn't needed. Couldn't your deploy task 
> just go at the bottom of your build script? Alternatively, 
> you can add an additional ant "builder" to your build track 
> and list it to run after the first one. I'm 95% sure that if 
> the first builder fails, the second one is not run.

If I put the 'deploy' task in as part of the build, then it would happen for
every build... which might be okay perhaps. I suppose if a build dies due to
a compile error, then the deploy task might not run, or could be forced not
to run.

Actually, the secondary builder would be a better scenario -- I had wondered
about that, and I guess I'll find out if there is a 5% chance it runs
regardless of the first builder failure. <grin>

Ideally, I would like the project owner to handle the BUILD process
(ant/maven/make/whatever) and then have a separate thing outside of the
project which handles the DEPLOY process. That way developers don't have to
understand the Release Engineer task of deployment. They will just provide
build artifacts in a standard directory ("<project>/dist/pname.ear") and the
system will know how to deploy to the DEV servers.

Thanks again for the help... so far, the UI could use a little help
(revision_log is ugly, and that left-nav-tree-thingy could use polish) ...
but in general I've managed to get things building in less time than cruise
control. :-)

I'll be back with more questions... should I move over to the Anthill Pro
list instead?

Cheers,
Tim