On Sun, Jun 12, 2016 at 2:48 PM, Baptiste Mathus <[email protected]> wrote:
> We have 90% of Maven builds. And we switched from maven to freestyle years > ago. > The things you list are not among the thing I miss, the only one I admit > was great was being able to do incremental builds easily. > > See inline below. > > 2016-06-09 9:39 GMT+02:00 Jorg Heymans <[email protected]>: > >> Just want to add to this >> >> - freestyle does not have "deploy artifacts" post build step >> > > Is `mvn clean deploy -DdeployAtEnd=true` somewhat what you want? > > What are you trying to achieve with that feature? I never used it, so I'm > curious about the use case. > It doesn't work if you want to deploy all your artifacts only if your build pass AND you want also to launch all tests (-Dmaven.test.failure.ignore=true) to have a global overview of all failures if something goes wrong. If you are using -Dmaven.test.failure.ignore=true and -DdeployAtEnd=true you'll deploy your artifacts when you have tests failures. Maven doesn't allow to do this for now. > > >> - freestyle does not have way to use a local maven repository per executor >> > > maven step, advanced, use private repository. That's in the UI. > No, there isn't the 'per executor' option which is the only option that allows to avoid conflicts of local repo access between jobs on the same agent and without consuming one repo per workspace. (Myself I prefer to use the private repo per job - thus per workspace - but I understand that the space used can be annoying) See https://issues.jenkins-ci.org/browse/JENKINS-17471 for many others subtleties between freestyle and maven jobs and few others issues like - JENKINS-5409 : freestyle projects doesn't support 'MAVEN_OPTS' global setting <https://issues.jenkins-ci.org/browse/JENKINS-5409> - JENKINS-24655 : In Maven jobs the option maven.test.failure.ignore is silently set to true by default <https://issues.jenkins-ci.org/browse/JENKINS-24655> - JENKINS-8412: Maven tasks in freestyle jobs aren't launched in batch mode <https://issues.jenkins-ci.org/browse/JENKINS-8412> - JENKINS-17471 : Maven Buildstep and Maven project are completely different <https://issues.jenkins-ci.org/browse/JENKINS-17471> - JENKINS-30460 : Environment settings are different in Pre/Post-Build "Invoke top-level Maven targets" and in Maven Job main build step <https://issues.jenkins-ci.org/browse/JENKINS-30460> > >> - freestyle does not have an easy way to use the maven release plugin >> > > That somewhat seems a definitive statement. As we do hundreds of maven > releases using freestyle jobs. Could you give details? > You can easily set up either the M2 Release plugin > <https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin> or the > more generic Release plugin > <https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin> to achieve > that (we used the first, and nowadays have settled on the latter). > > >> So yeah maybe it's evil and has issues, but the maven job type is really >> the only viable option for projects that heavily depend on maven mechanics. >> >> Jorg >> > Sadly Victor there is no automation to convert maven jobs to freestyle and there is no alternative for some features like the automatic triggering based on SNAPSHOTs, the post build deploy .. > >> >> On Monday, June 15, 2015 at 7:29:11 PM UTC+2, Jesse Farinacci wrote: >>> >>> There is no automated mechanism. >>> >>> On Mon, Jun 15, 2015 at 5:50 AM, Victor Noël <[email protected]> >>> wrote: >>> > Anybody? It seems an important issue to me… >>> > >>> > Thanks, >>> > >>> > Victor >>> > >>> > >>> > Le lundi 8 juin 2015 10:21:46 UTC+2, Victor Noël a écrit : >>> >> >>> >> Hi, >>> >> >>> >> Following the switch to Java 7+, many users have problem with the >>> >> Maven-style jobs: they are forbidden to execute them with a version >>> of Java >>> >> inferior to 7. >>> >> See for example https://issues.jenkins-ci.org/browse/JENKINS-28294. >>> >> >>> >> The common solution proposed by people is to switch to Freestyle >>> project: >>> >> there is more configuration to do, but the behaviour of the build >>> will be >>> >> more deterministic (see >>> >> >>> http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html >>> >> for example for more explanation of why anyway maven-style jobs >>> apparently >>> >> sucks). >>> >> >>> >> So, my question now is: how do I properly switch to a freestyle >>> project? >>> >> >>> >> In particular, my main concern is with dependencies and build >>> triggering: >>> >> - I want to be able to see the tree of builds like this: >>> >> >>> http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/265/ >>> >> - I want to see upstream and downstream projects like this: >>> >> >>> http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/ >>> >> - I want my jobs to be triggered when one of its dependencies was >>> built >>> >> (and not by checking every hours if a dependency has changed as one >>> of the >>> >> jenkins plugins do). >>> >> >>> >> Anybody has good suggestion to either do that, or to convince me I >>> don't >>> >> need it? >>> >> >>> >> Thank you :) >>> >> >>> >> Victor >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "Jenkins Users" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > To view this discussion on the web visit >>> > >>> https://groups.google.com/d/msgid/jenkinsci-users/d5e12297-218e-4564-bad1-03cac3cf6250%40googlegroups.com. >>> >>> > >>> > For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/a8424bc3-ccd6-48b1-b5f5-48849bd6848b%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/a8424bc3-ccd6-48b1-b5f5-48849bd6848b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS51ihbL3UEcxE1XUN6ZrEq0EbB-0XtQf%2B2TzF1CJ3Xfug%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS51ihbL3UEcxE1XUN6ZrEq0EbB-0XtQf%2B2TzF1CJ3Xfug%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAFNCU-_8Njz6wT-oaJCTmRtBHajzmfcv_XeEEanrJ7tprSD4ug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
