Hi all, We are having a little trouble with our release process and I was hoping for some insightful ideas how to ease our struggle. I'm sending this to the Jenkins list, because I think Jenkins is the tool, who can help with this.
We develop 5 different web applications (war files in ear files) which depends on a 20-such components. All those parts are different Maven projects in different Git repositories which have the same parent pom (although on different versions, which is another issue). The 5 web applications do not have the same release schedule and should be releasable any time. Whenever we adjust one of the applications and need changes in the underlying components, we update the version in the pom to the latest SNAPSHOT version and develop on both (or more) of the parts. Now we want a one press release, which should work its way down the dependency tree and release each snapshot, updating the versions in the pom along the way, until it reaches the deployable unit. I have been looking at the Maven Cascade Release Plugin [1] but that seems to need an aggregator project in which all the other projects are present. Could you provide some comments or insights about our situation and maybe give some hints how to ease our process? [1] https://wiki.jenkins-ci.org/display/JENKINS/Maven+Cascade+Release+Plugin With regards, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
