Re: ubuntu-4 Non-parseable settings /home/jenkins/.m2/settings.xml:

2016-06-08 Thread Keith W
Pono, Thanks for the update. Much appreciated. cheers, Keith On 8 June 2016 at 21:02, Pono Takamori wrote: > The job just built correctly on ubuntu-4. The jenkins-test-* images have > been updated to use the correct settings.xml file. You can file a ticket > on JIRA if this is a recurring is

Re: ubuntu-4 Non-parseable settings /home/jenkins/.m2/settings.xml:

2016-06-08 Thread Pono Takamori
The job just built correctly on ubuntu-4. The jenkins-test-* images have been updated to use the correct settings.xml file. You can file a ticket on JIRA if this is a recurring issue. Cheers, -Pono On Wed, Jun 8, 2016 at 7:51 PM, Keith W wrote: > Hello builds, > > Would anyone be able to take

Re: ubuntu-4 Non-parseable settings /home/jenkins/.m2/settings.xml:

2016-06-08 Thread Keith W
Hello builds, Would anyone be able to take a look at this please? Kind regards, Keith Wall. On 7 June 2016 at 14:41, Keith W wrote: > Hello Builds, > > > We are still seeing this error. It just occurred a few minutes ago on > jenkins-test-d2e. > > https://builds.apache.org/view/M-R/view/Qpid/jo

Re: Self-Adding Jenkins Build Machines

2016-06-08 Thread Michael Dürig
Thanks Nikhil, I'll relay this info back to the Jackrabbit PMC for deciding how to follow up on our side. Michael On 7.6.16 8:47 , Nikhil Khandelwal wrote: There was no further off-list discussion or conclusion here. Cordova project ended up giving up the idea of running our tests using Ap