Well, if you have configured your jobs in Hudson to be built whenever something changes in your SCM, you could compare the current date to the latest build. This would answer the question whether a release is required. As for releasing with Hudson, you might want to use the release plugin and start it with Hudson's CLI or wget. However, I don't think Hudson solves your specific requirements out-of-the-box (meaning: in an automated process). I think you would have to write a script which is then called every two weeks (e.g. with cron). But you would have to do that with Maven anyway.
Best regards, Eric > -----Ursprüngliche Nachricht----- > Von: Matt Milliss [mailto:[email protected]] > Gesendet: Montag, 14. September 2009 01:00 > An: Maven Users List > Betreff: Re: Automated release process > > Thanks Thomas, > > we're using hudson as our CI server but I don't really > understand how this > will solve my problem for me. We've got hudson setup to > deploy snapshots to > our archiva repository on every svn commit and we're using > unique/timestamped snapshots, but not really sure how hudson can > automatically perform a release:prepare/perform step at a > given point in > time ie every 2 weeks on only projects have changed since the > last release. > Am I missing some feature that hudson supplies? Or am I just > doing things > wrong all over the place? > > Cheers > Matt > > Thomas Sundberg wrote: > > Hi! > > It sounds as you need a CI server. It would solve your issue. > Take a look at > > CruiseControl:http://cruisecontrol.sourceforge.net/ > > Hudson:https://hudson.dev.java.net/ > > /Thomas > > On Thu, Sep 10, 2009 at 13:10, Matt Milliss <[email protected]> > <[email protected]> wrote: > > > I work at a company that has around 10 applications, each > application is a > maven project, each of which may or may not get modified in a > given 2 week > iteration. At the end of every iteration I want an automated > process for > checking which applications have been modified since the last > release and > then release only those applications. Something along the lines of the > following; > > 1. retrieve previous release version from our archiva repo > 2. in subversion compare that versions tag against trunk to see any > differences > 3. if any differences then perform a release of that project > 4. repeat for each application > > I've been trying to find a maven way of doing this but > haven't had any luck, > has anybody done something similar with success. > > Cheers > Matt Milliss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
