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 <dant...@gmail.com> 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 <francois.ma...@gmail.com> > 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: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > -- 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.
