Re: Jenkins and Maven

about had it with bamboo, and are dusting off our old Jenkins > instance. > > > > I recall some messages here about things _not_ to do with Jenkins and > > Maven. Do we avoid the 'maven build type' altogether and just run > > Maven from the shell, or is my memory faulty?

Re: Jenkins and Maven

had it with bamboo, and are dusting off our old Jenkins instance. > > I recall some messages here about things _not_ to do with Jenkins and > Maven. Do we avoid the 'maven build type' altogether and just run > Maven from the shell, or is my memory faulty

Re: Jenkins and Maven

For pipeline you want to use the mavenLocalRepo property of the withMaven step in the https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Maven+Plugin On 13 October 2016 at 16:41, Benson Margulies <bimargul...@gmail.com> wrote: > So, here's a specific puzzle. I want to enable multiple

RE: Jenkins and Maven

To make concurrent Jenkins builds work, simply enable the "Use private Maven repository" option in the Jenkins Maven build jobs and select the appropriate "Strategy" (e.g., "Local to the workspace" or "Local to the executor"). This works fine for us...

Re: Jenkins and Maven

You install https://github.com/takari/takari-local-repository Or fix the bug from, like, 2007 ? https://issues.apache.org/jira/browse/MNG-2802 On Thu, Oct 13, 2016 at 4:41 PM, Benson Margulies wrote: > So, here's a specific puzzle. I want to enable multiple branches in >

Re: Jenkins and Maven

So, here's a specific puzzle. I want to enable multiple branches in the Jenkins job and concurrent builds. How do I avoid two jobs trying to write the same local repo at the same time? - To unsubscribe, e-mail:

RE: Jenkins and Maven

into a Maven bug/limitation (like MNG-5889). -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Thursday, October 13, 2016 9:39 AM To: Maven Users List Subject: Re: Jenkins and Maven When they work, they work... when they don't work they blow up in your

Re: Jenkins and Maven

that my day job is actually developing Jenkins... feel free to take my opinions however you see fit On 13 October 2016 at 15:24, Robert Patrick <robert.patr...@oracle.com> wrote: > Well... Some of us, my team included, are using the Maven jobs in Jenkins > and they generally works

RE: Jenkins and Maven

Well... Some of us, my team included, are using the Maven jobs in Jenkins and they generally works fine for our projects (and is much simpler to configure). Be warned that Maven 3.3 support is still busted for projects that use .mvn/maven.config waiting on https://issues.apache.org/jira

Re: Jenkins and Maven

.alan.conno...@gmail.com> wrote: > >> https://javaadventure.blogspot.ie/2013/11/jenkins- >> maven-job-type-considered-evil.html >> is the message from your friendly neighbourhood Apache Maven PMC member and >> Jenkins committer! >> >> Two options: >&

Re: Jenkins and Maven

+1 for pipeline build. On Thu, Oct 13, 2016 at 10:15 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > https://javaadventure.blogspot.ie/2013/11/jenkins- > maven-job-type-considered-evil.html > is the message from your friendly neighbourhood Apache Maven PMC membe

Re: Jenkins and Maven

https://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html is the message from your friendly neighbourhood Apache Maven PMC member and Jenkins committer! Two options: 1. (oldschool) Freestyle Job with a Maven build step 2. (coolkids) Multibranch Pipeline Job

Jenkins and Maven

We've about had it with bamboo, and are dusting off our old Jenkins instance. I recall some messages here about things _not_ to do with Jenkins and Maven. Do we avoid the 'maven build type' altogether and just run Maven from the shell, or is my memory faulty? Anything else

Jenkins via Maven deploy to Nexus snapshot repository issue

] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.760s [INFO] Finished at: Mon Sep 22 12:25:39 EDT 2014 -- View this message in context: http://maven.40175.n5.nabble.com/Jenkins-via-Maven-deploy