thully wrote:
> We can run mvn deploy whenever we make an RC build - however, the problem
> with that ends up being that we are deploying artifacts to our repository
> that may not be the final release. That's what we want to avoid - while we
> can re-deploy if we end up doing a second RC, the lac
Our issue isn't with deploying some artifacts prematurely when an install
fails - that's not normally a problem, since we've generally done at least
one successful mvn install before doing an mvn deploy.
The issue is that when we're in RC phase, we want to give our artifacts
version numbers as if
Seems like a lot of time fighting what Apache Maven does. Usually a
good smell that you're doing something wrong.
Use installAtEnd / deployAtEnd. Bytes are cheap, just burn them and
move on to a real problem.
On Wed, May 4, 2016 at 3:48 PM, Mirko Friedenhagen
wrote:
> Hello,
>
> what about enhan
I had an experiment plugin that would capture all the attached artifacts
and record them in an on-disk file. Then in another maven session you could
attach them back again. There were some bugs but it seemed promising
On Wednesday 4 May 2016, Mirko Friedenhagen wrote:
> Hello,
>
> what about enh
Hello,
what about enhancing the install plugin with a list of the latest installs
and creating a mojo deploy:deploy-latest-install?
Regards
Mirko
--
Sent from my mobile
Am 03.05.2016 18:15 schrieb "Stephen Connolly" <
stephen.alan.conno...@gmail.com>:
> I think that if your SCM supports the opt
Very promising, may need to do some scm provider work to support other SCM
like Perforce?
Thanks
-D
On Wed, May 4, 2016 at 12:20 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Here's an embryonic idea I had for doing Continuous Delivery with Maven
>
>
> https://www.cloudbees.c
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
We can run mvn deploy whenever we make an RC build - however, the problem
with that ends up being that we are deploying artifacts to our repository
that may not be the final release. That's what we want to avoid - while we
can re-deploy if we end up doing a second RC, the lack of version
differenti