My original question was
>>1. How to distinguish snapshot build versions correctly? So that one
>>snapshot build would not overwrite previous one in the repository.
>
>You don't, that's not the purpose. If you truly care about a particular
>snapshot version, then it should have been a release. I
> In a previous company, the snapshots were not used by qa, all
> deliveries to qa where release builds. We used a 4 digit
> versioning where the last number was just a build number. We
> did this because it wasn't known ahead of time if a given
> build would pass qa and be officially release
>So your formal releases are produced by manually running the release
> >plugin? And if it fails, you manually do a rollback,
> depending on the
> >failure?
>
> Yes, we manually roll it back. It's not too bad with svn, but
> a bit annoying I'll admit. We haven't tackled the release tools yet.
>Regarding snapshots and the way your QA works it all looks like you have
>adjusted your team workflow to the features the maven tool provides.
Yes, this comes from years of using the tool, but is also adapted to our
current environment.
>And
>these features are not so flexible to cover all re
ox [mailto:bri...@sonatype.com]
> Sent: Tuesday, April 07, 2009 11:16 PM
> To: Maven Users List
> Cc: Guillaume Goulet; Kevin Coupland; Kyle Blaney
> Subject: RE: Understanding SNAPSHOTS
>
> >1. How to distinguish snapshot build versions correctly? So that one
> >snapshot
ething in the online
description).
Best Regards,
Sergey Shcherbakov.
-Original Message-
From: Brian Fox [mailto:bri...@sonatype.com]
Sent: Tuesday, April 07, 2009 11:16 PM
To: Maven Users List
Cc: Guillaume Goulet; Kevin Coupland; Kyle Blaney
Subject: RE: Understanding SNAPSHOTS
>1. How to dis
>So your formal releases are produced by manually running the release
>plugin? And if it fails, you manually do a rollback, depending on the
>failure?
Yes, we manually roll it back. It's not too bad with svn, but a bit annoying
I'll admit. We haven't tackled the release
tools yet.
>Some of our
2009/4/7 Todd Thiessen
> > ...that is we decide when a release is ready and
> > use the release plugin to do this. The CI is only producing
> > snapshots on a constant basis.
>
> So your formal releases are produced by manually running the release
> plugin? And if it fails, you manually do a roll
> ...that is we decide when a release is ready and
> use the release plugin to do this. The CI is only producing
> snapshots on a constant basis.
So your formal releases are produced by manually running the release
plugin? And if it fails, you manually do a rollback, depending on the
failure?
S
Kevin (BVW:9T16);
> Blaney, Kyle (BVW:9T16)
> Subject: RE: Understanding SNAPSHOTS
>
> Hello,
>
> We have our CI system setup to build after every commit for
> verification. It happens to build on a grid with multiple
> OS's and one of them deploys a snapshot t
>1. How to distinguish snapshot build versions correctly? So that one
>snapshot build would not overwrite previous one in the repository.
You don't, that's not the purpose. If you truly care about a particular
snapshot version, then it should have been a
release. It's meant only for looking at th
Hello,
We have our CI system setup to build after every commit for verification. It
happens to build on a grid with multiple
OS's and one of them deploys a snapshot to our Nexus repo. Our QA grabs the
latest snapshot of the application at
various times and validates the fixes against it. (they l
en Users List
> Cc: Goulet, Guillaume (CAR:LSBA); Coupland, Kevin (BVW:9T16);
> Blaney, Kyle (BVW:9T16)
> Subject: RE: Understanding SNAPSHOTS
>
> Hi Todd,
>
> I came to exactly same conclusions as you did and even
> applied that approach in our team.
> I have set up our
ers List
> Cc: Goulet, Guillaume (CAR:LSBA); Coupland, Kevin (BVW:9T16);
> Blaney, Kyle (BVW:9T16)
> Subject: RE: Understanding SNAPSHOTS
>
> Hi Todd,
>
> I came to exactly same conclusions as you did and even
> applied that approach in our team.
> I have set up our proje
Hi Todd,
I came to exactly same conclusions as you did and even applied that
approach in our team.
I have set up our projects to use local intranet repository for snapshot
builds and external production repository for released builds.
But it has definitely some inconveniences. And I am wondering
15 matches
Mail list logo
