Re: How can we choose the right maven version for our build?

"mvn" command is picked up first even if it's on the existing > PATH. > > David > > -Original Message- > From: Jarek Jarcec Cecho [mailto:jar...@gmail.com] On Behalf Of Jarek Jarcec > Cecho > Sent: Friday, 16 October 2015 6:21 AM > To: builds@

Re: How can we choose the right maven version for our build?

Any ideas how to pick up the proper version of maven? Jarcec > On Aug 24, 2015, at 1:20 PM, Jarek Jarcec Cecho wrote: > > I have a job that is quite regularly failing with: > > Error resolving version for 'org.codehaus.mojo:findbugs-maven-plugin': Plugin >

How can we choose the right maven version for our build?

I have a job that is quite regularly failing with: Error resolving version for 'org.codehaus.mojo:findbugs-maven-plugin': Plugin requires Maven version 3.0.1 Looking into the job’s configuration, I don’t see any way to specify maven version (similarly as we do for let say java). It seems that w

Re: FYI - disabled timer triggers across the board on builds.apache.org

It turned out that I’ve incorrectly put the “run every 10 minutes” to “poll SCM” field rather then to “Run periodically” field. Fixed. Jarcec > On Aug 21, 2015, at 9:29 AM, Jarek Jarcec Cecho wrote: > > No worries, I completely get why we made this change across the board. I > a

Re: What is the process of reporting dead slaves

Got it, it looks much better now - thank you! Jarcec > On Aug 21, 2015, at 9:33 AM, Andrew Bayer wrote: > > It's not the slaves, it's the master itself. > > A. > > On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho > wrote: > >> Thanks Andrew!

Re: What is the process of reporting dead slaves

ll take a look in 30 minutes or so. > On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > >> Looking at Jenkins queue - there is 132 queued jobs and only 4 working >> executors :) All the others are marked as “DEAD”. >> >> I’m wondering what is the process

Re: FYI - disabled timer triggers across the board on builds.apache.org

ps, sorry about that! > On Aug 21, 2015 12:02, "Jarek Jarcec Cecho" wrote: > >> I’ve noticed that this change has pretty much disabled Hadoop world >> spefici precommit [1] hook as this job is running every 10 minutes and >> fetching updates from JIRA, rather then

What is the process of reporting dead slaves

Looking at Jenkins queue - there is 132 queued jobs and only 4 working executors :) All the others are marked as “DEAD”. I’m wondering what is the process of reporting that? Should I create BUILDS or INFRA JIRA, or just send email to this group or something completely else? Jarcec

Re: FYI - disabled timer triggers across the board on builds.apache.org

I’ve noticed that this change has pretty much disabled Hadoop world spefici precommit [1] hook as this job is running every 10 minutes and fetching updates from JIRA, rather then following any repository. I’ve put back the “run every 10 minutes”. This job is usually done in less then 30 seconds,

Adding Sqoop pre commit hook on builds.apache.org

Sqoop community would like to ask for configuring pre commit hook per [1] in the PreCommit-Admin job [2]. We've created custom pre commit build called PreCommit-SQOOP-Build [3] via SQOOP-1082 and the job seems to be working just fine. Thank you very much in advance! Jarcec Links: 1: http://wi