ConcurrentContinuous Delivery Maven Builds

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

ConcurrentContinuous Delivery Maven Builds

Dan Tran
Hi

I have a requirement to run concurrent maven continuous deliver style.
Each new commit/PR triggers new pipeline with unique version.

Since maven deployment also pushing maven-metadata.xml which can be
corrupted for concurrent pipeplines

I wonder if Artifactory or Nexus have some type of protection for this
scenario?

Thanks

-Dan
Reply | Threaded
Open this post in threaded view
|

Re: ConcurrentContinuous Delivery Maven Builds

Paul Hammant
Continuous Delivery is into QA / UAT, right?
Continuous Deployment is into Prod.

You need the jars in Artifactory because other teams depend on them?  If
not then just deploy to QA/UAT and don't drop jars (or anything) into
Nexus/Artifactory/WebDAV.

- Paul



On Wed, Mar 14, 2018 at 4:31 AM, Dan Tran <[hidden email]> wrote:

> Hi
>
> I have a requirement to run concurrent maven continuous deliver style.
> Each new commit/PR triggers new pipeline with unique version.
>
> Since maven deployment also pushing maven-metadata.xml which can be
> corrupted for concurrent pipeplines
>
> I wonder if Artifactory or Nexus have some type of protection for this
> scenario?
>
> Thanks
>
> -Dan
>



--
Paul Hammant DevOps <https://devops.paulhammant.com> Let me give your
enterprise a step by step plan to get out of the hell of crazy branching
models (ClearCase maybe?) and into the world of high-throughput CD on
DevOps foundations.
Reply | Threaded
Open this post in threaded view
|

Re: ConcurrentContinuous Delivery Maven Builds

Francois MAROT
In reply to this post by Dan Tran
What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
which is solved in Maven 3.5.2 (even 3.5.1 I think) ?



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ConcurrentContinuous Delivery Maven Builds

Dan Tran
@Paul yes the final build artifacts go to QA. I guess I can instrument
Maven only deploy the necessary files.  But I still need to deploy full
snapshot build once a day

@Francois, for my case, it very very possible that 2 parallel pipelines
pushing same artifact ( different versions) to maven repo and step on each
other maven-metadata.xml files

Thanks

-D

On Wed, Mar 14, 2018 at 2:14 PM, Francois MAROT <[hidden email]>
wrote:

> What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
> Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
> which is solved in Maven 3.5.2 (even 3.5.1 I think) ?
>
>
>
> --
> Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: ConcurrentContinuous Delivery Maven Builds

Paul Hammant
Have a Jenkins job that runs at 10pm that picks up the *last green build*
of the day and re-does it (skipping tests this time) but goes on to push
the war file (or equiv) to the appropriate QA machines servers.

That builds ran in parallel earlier in the day, is not longer important.
Again, skip the pushing to Artifactory/Nexus for QA builds.

And that's CI not CD by the way (CD would be every commit into an env if
the build passes at the bleeding edge or every N builds through the day
from trunk/master).

- Paul

On Wed, Mar 14, 2018 at 5:44 PM, Dan Tran <[hidden email]> wrote:

> @Paul yes the final build artifacts go to QA. I guess I can instrument
> Maven only deploy the necessary files.  But I still need to deploy full
> snapshot build once a day
>
> @Francois, for my case, it very very possible that 2 parallel pipelines
> pushing same artifact ( different versions) to maven repo and step on each
> other maven-metadata.xml files
>
> Thanks
>
> -D
>
> On Wed, Mar 14, 2018 at 2:14 PM, Francois MAROT <[hidden email]>
> wrote:
>
> > What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
> > Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
> > which is solved in Maven 3.5.2 (even 3.5.1 I think) ?
> >
> >
> >
> > --
> > Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>



--
Paul Hammant DevOps <https://devops.paulhammant.com> Let me give your
enterprise a step by step plan to get out of the hell of crazy branching
models (ClearCase maybe?) and into the world of high-throughput CD on
DevOps foundations.