www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Hudson and Apache Releasing
Date Wed, 02 Mar 2011 10:27:47 GMT
If we check the box in a Job configuration that says "Deploy artifacts to the
Maven Repository" and specify the Apache Nexus Snapshot repo, what happens if a
build starts right at the moment when the Apache Release plugin has renamed the
POMs to a non-Snapshot release version and checked those into trunk, so it can
tag a release candidate?

I presume the build might check-out from trunk a release version and build it. 
Assuming the build completes without error, the post-processing would attempt to
upload this non-Snapshot to the Apache Nexus snapshot repo (the URL in the job
configuration says:

https://repository.apache.org/content/repositories/snapshots )

Would our Nexus configuration or the Hudson Maven plugin realize that something
was amiss, in this case, and block the deploy to the repo? 

If not, is the right "best practice" to disable deployment in the job build
settings while doing release work, and re-enable it afterwards?

I found by googling this plugin for hudson:
http://code.google.com/p/maven-hudson-ext-plugin/ which explicitly says it
recognizes this situation and doesn't upload.  But I don't think this is the
plugin we have installed, because the label on the "Build Settings" is different.

-Marshall Schor

Mime
View raw message