On 9 February 2018 at 06:54, Hervé BOUTEMY <[email protected]> wrote:
> Le vendredi 9 février 2018, 02:16:10 CET Olivier Lamy a écrit : > > Thanks! > > I will have a look for Wagon. > thank you > > > > > Do we deploy automatically SNAPSHOT or not? > currently not: I'd like to do it, I think it's natural > but Stephen, who masters the new Jenkins build configuration, is not > positive > on the idea > OMG it might be really complicated... :P > and nobody really started a clean discussion on that > > > because of jdk10 issue for surefire, I currently have external projects > > depending on those snapshot. > to be concrete, currently, when I want to consume a SNAPSHOT after a > release > has been done, I have to do manually the "mvn deploy" from my computer > and each time I did this, I can confirm that it was the first SNAPSHOT > that was > deployed (even if the release has been done a few weeks ago) > I'd like to have auto build of downstream projects as well... changes of a shared lib should rebuild plugins depending on it etc... > > > IMHO might be good to have auto deploy so quick feedback from early > > testers/adopters > +1 > > let's start the discussion: I'm convinced this is natural for a CI job to > deploy SNAPSHOTs automatically to SNAPSHOT repository > and after thinking at it seriously, I think the fear Stephen has is valid > only > on *triggering a build based on a new SNAPSHOT availability*, but not > really > on *deploying SNAPSHOTs as part of continuous build* > the only question to me is how to code it precisely, to be sure the deploy > happens only once (and not on each OS+JDK configuration), and as much as > possible only if the build is fully successful (here, IIUC, the detection > of > "successful build" is currently not reliable) > Regards, > > Hervé > > > > > On 8 February 2018 at 22:25, Hervé BOUTEMY <[email protected]> > wrote: > > > ok, I did the cleanup > > > > > > Tibor, I think there is cleanup to do on Surefire jobs: don't hesitate > to > > > do it > > > > > > I don't know for Wagon jobs > > > > > > > > > The cleanup I didn't do is the cleanup on maven-master-release-* > > > https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ > > > > > > I just disabled the jobs: if nobody objects, I'll delete the jobs and > even > > > the > > > view in 1 week > > > > > > Regards, > > > > > > Hervé > > > > > > Le mercredi 24 janvier 2018, 07:41:32 CET Hervé BOUTEMY a écrit : > > > > Le mardi 23 janvier 2018, 20:57:42 CET Karl Heinz Marbaise a écrit : > > > > > >> 3. > > > > > >> https://builds.apache.org/view/M-R/view/Maven/job/core-> > > > > integration-test > > > > > > > > >> in > > > > > >> g-m aven-3-embedded/ > > > > > > > > > > > > I'd like to keep this one, since it's a reference in embedded > mode > > > > > > (faster > > > > > > execution) > > > > > > > > > > Our default Job for Maven Core [1] is running with embedded mode.. > > > > > > > > > > > > > > > [1]: https://builds.apache.org/job/maven-wip/job/maven/ > > > > > > > > ok, thanks for the info (I could have found myself...) > > > > > > > > then +1 to drop this job also > > > > > > > > and while at it > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven- > 3.x-jenkinsfile/ > > > > > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > ------------------------------------------------------------ > --------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
