There's a setup section on the wiki page which has the necessary info on setting up Hudson. The staging plugin is part of the 'tom' branch which is linked to from the page.
On Tue, Jul 8, 2008 at 9:59 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > Is the code anywhere? > > I'm interested in the process, but have gone down the Drools workflow way, > and I'm trying to work on the promotion from Nexus. But I'll definitely take > a look at code. > > On 8-Jul-08, at 3:40 PM, Tom Huybrechts wrote: > >> On Mon, Jul 7, 2008 at 5:47 PM, John Casey <[EMAIL PROTECTED]> wrote: >>> >>> >>> Jason van Zyl wrote: >>>> >>>> There are groups there for Maven 2.1, Plexus, Maven IDE (really embedder >>>> consumers), and I will also limit the plugins to the default lifecycles >>>> of >>>> the commonly used packagings like JAR, and WAR. John has also started >>>> creating automated ways to release to stage, and subsequent promotion >>>> upon >>>> success. So for any component in the tool chain there will be a way to >>>> do a >>>> consistent release from a canonical machine. >>> >>> Just for posterity (if we're going to be using this as an official >>> release >>> vector for the entire project): >>> >>> Jason's referring to a ruby script I wrote to lookup the version string >>> for >>> a particular staged project, for use in the stage:copy mojo. This allows >>> us >>> to setup generic promotion scripts in a CI environment like Hudson. I've >>> committed this script to: >>> https://svn.apache.org/repos/asf/maven/sandbox/trunk/scripts. >>> >>> The rest of this release infrastructure has simply been configuration of >>> hudson and nexus - nexus, to provide a staging ground for releases - to >>> configure release jobs that deploy to this staging location instead of >>> the >>> real release repository...just generalizing on configuration that we all >>> have in our personal settings.xml files by now. Jason's credentials are >>> used >>> for SVN and SSH where necessary, and I've created a new GPG key for use >>> in >>> this CI system, then signed it with my own key. That key ID is: >>> 84B54612. >>> >>> To echo Jason, the goal here is to create an environment that - if not >>> perfectly flawless - is at least a known quantity. Just as we've moved in >>> the direction of pointing to our CI servers as the definitive point of >>> reference for our unit and integration tests (though we're not quite >>> there >>> yet), we need to be releasing Maven artifacts from a similarly definitive >>> environment. In principle, the configuration and script I've written >>> (above) >>> should enable any team to enable a similar release infrastructure for >>> their >>> own projects. >>> >>> -john >>>> >> >> I tried to automate part of the Maven release process (including >> staging a release and voting on it) as a demo of Hudson-JBPM >> integration. >> This is a work in progress, but if you're interested, you can find >> more info at http://hudson.gotdns.com/wiki/display/HUDSON/JBPM+Plugin >> >> Tom >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > Three people can keep a secret provided two of them are dead. > > -- Unknown > > > --------------------------------------------------------------------- > 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]
