Hi Stephen, nice blog.
There are a few things I'd like to share:
- The maven-release-plugin does several checks which ensures that you have
a reproducible artifact, where checking on SNAPSHOT dependencies is one of
the most important ones. (you can find a lot patterns based on the
versions-maven-plugin on the web, but they forget these checks)
- I still have this wish to have support a couple of strategies within the
maven-release-plugin, this could be one as well.
In a continuous environment is becomes more and more important to be able
to reproduce issues, which can be hard when things keep changing. This
might even work with SNAPSHOT dependencies if your can get the
distributable (either the deployable or executable artifact, assuming they
contain all the required dependencies) and have a testing setup which can
test with this artifact. If you can reproduce it here, you can (re)write
it as an appropriate test and fix it.
So next to all the current tests you need to do regression tests on the
distributable as well.
As long as this is not possible or secured in your pipeline, you should
NEVER EVER want to depend on SNAPSHOT-dependencies.
thanks,
Robert
On Wed, 04 May 2016 21:20:01 +0200, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
Here's an embryonic idea I had for doing Continuous Delivery with Maven
https://www.cloudbees.com/blog/new-way-do-continuous-delivery-maven-and-jenkins-pipeline
Probably needs a little fleshing out.
-Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
