We intend to use Hudson for releasing our components. This will be a manually triggered process and I have been looking at the batch task plugin (http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin) which partially does what I want.

We would like to avoid having to start releasing components on the lowest level and then work upwards the food chain. Instead it would be very nice if one can trigger the release cycle on the highest level which causes lower level dependencies to be released as well (if there any changes but that is handled by the build script). Of course, this requires that all ivy.xml's are in synch or at least using latest.release.

This could perhaps be realized by a reversed Ivy plugin, i.e. before a project is built, all its dependencies are built. Then, by having a separate release project (invoking a special Ant target) on the highest level, I can achieve the above. It would of course be even better if a project could be reused but that might be very complicated.

Or am I way off here?