> From: bmat...@batmat.net
> Date: Sat, 15 Feb 2014 22:07:26 +0100
> Subject: Re: Possible build collision between CI snapshot build and Release
> build
> To: users@maven.apache.org
>
> OK, so this has to be CVCS (svn and so on) specific?
> I didn't check
Baptiste, you are totally correct. For my case, I use one staging repo per
project ( long story), so there is a very small window of collision.
Thank you for this very good advice.
-Dan
On Sat, Feb 15, 2014 at 1:07 PM, Baptiste Mathus wrote:
> OK, so this has to be CVCS (svn and so on) specif
OK, so this has to be CVCS (svn and so on) specific?
I didn't check if the release-plugin commits + push each time. If this is
so, it should be fixed so that this cannot happen.
I would say that though this is a valid technical concern, it's very
unlikely to happen in real life.
Let's take an exa
hmm, time for me to upgrade my hudson/jenkins :-)
-D
On Sat, Feb 15, 2014 at 10:46 AM, Robert Scholte wrote:
> Hi,
>
> Isn't it the other way around?
> There's only a critical situation: when the maven-release-plugin has
> committed the non-SNAPSHOT poms or when it is busy tagging. In such case
Thank you all, enforcer rule is the way to go. I will put it at my company
top level pom and disable this rule at release time.
-Dan
On Sat, Feb 15, 2014 at 8:52 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Or filter commits where the log message starts with m-r-p's prefix
>
Hi,
Isn't it the other way around?
There's only a critical situation: when the maven-release-plugin has
committed the non-SNAPSHOT poms or when it is busy tagging. In such cases
the CI can be triggered by SCM changes, but it shouldn't continue since
there's a final version.
I think most CI'
Or filter commits where the log message starts with m-r-p's prefix
On Saturday, 15 February 2014, Stuart McCulloch wrote:
> On 15 February 2014 15:51, Thomas Broyer >
> wrote:
>
> > On Sat, Feb 15, 2014 at 4:18 PM, Baptiste Mathus
> >
> >
> > wrote:
> >
> > > Hi Dan,
> > > Not sure what you me
On 15 February 2014 15:51, Thomas Broyer wrote:
> On Sat, Feb 15, 2014 at 4:18 PM, Baptiste Mathus
> wrote:
>
> > Hi Dan,
> > Not sure what you mean. You say "CI", are you taking about a specific
> > server? If Jenkins for example, wouldn't it then be more a Jenkins user
> ml
> > question?
> >
>
On Sat, Feb 15, 2014 at 4:18 PM, Baptiste Mathus wrote:
> Hi Dan,
> Not sure what you mean. You say "CI", are you taking about a specific
> server? If Jenkins for example, wouldn't it then be more a Jenkins user ml
> question?
>
> And I don't see how a snapshot build could interfere with another
Hi Dan,
Not sure what you mean. You say "CI", are you taking about a specific
server? If Jenkins for example, wouldn't it then be more a Jenkins user ml
question?
And I don't see how a snapshot build could interfere with another build
with a release version.
Could you give details about your issue
Hello
It is possible that while release:prepare cutting the tag and CI for
snapshot build wakeup at the same time. Is there a way to prevent this?
like a a profile to fail the build if the version happen to be a release
version. Ie is there a way to detect this in a profile?
I currently have t
11 matches
Mail list logo
