R – continuous integration based on maven2

continuous integrationmaven-2shellsvn

I am trying to figure out how to setup continuous integration using maven.

What I want is:

Check for new stuff in SVN
If changes are detected, check them out
Build and deploy

I think all of this can be pushed into some shell script to make it be invoked by cron. Thus we will have automated continuous integration (nightly builds, for example)

I know that maven has SCM plugin for working with version control systems, but I don't know how to make it check for changes in repository and based on the results launch checkout.

So I am asking the audience 🙂

PS I forget to mention – I am NOT INTERESTING in any of existing applications! They are too heavy for my VPS server. Please do not advise them

Best Answer

Take a look at Hudson. It's free, open-source, actively developed, has dozens of useful plugins, has great Maven2 support, and is all around awesome.

It's also frequently discussed on Stack Overflow.

Related Solutions

Recommendations regarding Continuous Integration systems

Cruise Control.net (ccnet) does everything you are looking for. Its pretty easy to use, just make sure if you are going to run it as a service, you give it an account and don't make it run as network service, that way you can give it rights on intranet boxes and have it do xcopy deploys.

It has all kinds of email modes, on failure, on all, on fix after failure, and many many more.

How to maven be used in a continuous integration situation to install versioned artifacts in the repository

Sounds like you want to build SNAPSHOT versions with unique versions.

So, in your POM declare the version as:

<version>#.#.#-SNAPSHOT</version>

Then, in the distributionManagement section of your POM, enable unique versions for the snapshotRepository via (see Maven's POM reference on this):

<snapshotRepository>
  <uniqueVersion>true</uniqueVersion>
  <id>your-snapshot-repo-id</id>
  <name>Your Snapshots</name>
  <url>http://your-snapshot-repo-url/maven</url>
</snapshotRepository>

FYI, note that Maven conventions recommend versions be declared as major.minor.revision. So, 1.0.25 instead of 1.0.0.25. If you're able to use this versioning scheme, things will work more smoothly in a Maven world.

Best Answer

Related Solutions

Recommendations regarding Continuous Integration systems

How to maven be used in a continuous integration situation to install versioned artifacts in the repository

Related Topic