Build when an artifact is deployed

[hezjing]

Hi

I would like to create a Jenkins job which will monitor an artifact from the Maven repository, and start the build whenever the artifact is deployed.

Note that in this case, someone may re-deploy the same version of artifact many times and the build should also be started too!

Any idea?

--

Hez

[Manuel Doninger]

If that artifacts are snapshots, then you can try the plugin "Maven
Dependency Update Trigger"
(http://wiki.jenkins-ci.org/display/JENKINS/Maven+Dependency+Update+trigger).

Manuel

[Swindells, Thomas]

And if they aren't snapshots then whoever is redeploying the same version should be shot! It means you no longer have traceable, reproducible builds or any firm way of knowing what you have actually built with.

Thomas

**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

[Olivier Lamy]

With my maven committer hat, I can only say it's a bad practice about
redeploying artifact with same version.

What will happen for people who already have it in their local repo or
if this artifact is "cache" in your repoman ?

You ask folks to cleanup their local repo ?

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

2011/3/9 Swindells, Thomas <TSwin...@nds.com>:

[hezjing]

I agreed that we must not redeploy the non-snapshot version :-)

As for the snapshot version, imagine that your project is depending on a library which is also in active development. Since the library is still in active development, the CI server will automatically build and deploy the same snapshot version whenever there changes committed.

How can I configure Jenkins to start building the project as soon as the CI server deployed the library in 1.0-SNAPSHOT ... 1.0-SNAPSHOT, 1.0, 2.0 and so on?

In this case, the dependency update trigger plugin may not be useful because it only monitor the snapshot.

--

Hez

[Olivier Lamy]

Maybe by asking for an enhancement in the plugin "Maven Dependency
Update Trigger" :-)

A new configuration option "Check non snapshot artifacts too" (in this
all downloaded artifacts will schedule a build)
Can you load a jira entry and assign it to me ?

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

2011/3/15 hezjing <hez...@gmail.com>:

[hezjing]

Hi Olivier

I have created http://issues.jenkins-ci.org/browse/JENKINS-9068

But I didn't assign the issue to you because I cannot find your name there :D

--

Hez

[Olivier Lamy]

Hello,
Not a problem, there is an automatic assignee for the module
maven-dependency-update-trigger to myself (olamy).
So I have been informed :-).
Not a lot of spare time this week, I will try to work on this next
week. (do not hesitate to ping me if you don't see any progress)

Thanks,

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

2011/3/16 hezjing <hez...@gmail.com>: