Continuous Snapshots

Posted in Services by Ben Walding on June 25, 2009 3 Comments

For those of you who are new to Codehaus, or are wondering what capabilities are out there, we will be slowly covering the documented and (sadly too frequent) undocumented features of Codehaus.

If you have configured  a build in Bamboo, then you would know that using continuous integration (CI) can be a great way to build packages for users who want to use the latest and greatest, but don’t have the time nor the patience to build these packages.

Maven Configuration

In order to make Maven deploy your snapshots to the appropriate area on the Bamboo server, you will need to configure the snapshot repository using your pom.xml

Please review the pom.xml fragment found at profile.xml

Please note that any process is free to write / remove files under /opt/snapshot.ci.codehaus.org/ – so please be respectfui of other projects. If there is too much contention we will be forced down the totalitarian path – and we don’t want this.

Deploy

You can then deploy your artifacts using the deploy plugin.

maven deploy:deploy

Cleanup

At some point; the archive will become fat and unwieldy. We will implement a pruning mechanism to remove old artifacts at that point.

The upshot of this – don’t rely on versioned SNAPSHOTS being this repository for ever.  Also note that this applies as a general rule to artifacts help in the main snapshot repository – http://snapshots.repository.codehaus.org/

Issues?

As always contact support with any issues.

(We’ve just pieced this altogether from the support requests we’ve handled. If there is any nuance we’ve messed up, let us know!)

distributionManagement

Post to Twitter Tweet This Post Post to Delicious Delicious

Tags:
Comments
  • Kalle Korhonen:

    Probably worth documenting how to configure CI snapshot deploy via Maven. We (Tynamo project) use:

    bamboo

    tynamo-codehaus-ci
    Official snapshot repository available from Codehaus’ Bamboo server
    file:///opt/ci.repository.codehaus.org/

    This way we can also manual snapshots via dav if need be. Our Bamboo builds simply activate “bamboo” profile by specifying mvn -P bamboo clean deploy.

    Reply October 28, 2009 at 4:21 am
  • Kalle Korhonen:

    Bah, comment system strips out all tags. Left to reader to figure out where profiles, profile etc. Maven elements go in the previous post :)

    Reply October 28, 2009 at 4:23 am
Leave a Comment