Jenkins build failure console output

I am receiving this error message in the output at the end. It says it can not find the root pom.xml. The reason is that the build workspace directory is empty: /var/lib/jenkins/workspace/bbword-build/, which means Jenkins fails to copy the project files (including the root pom.xml) to

Connection time out issues

My setup: master running on ubuntu 3 x slaves running on OSX I am running 3 builds at one time. When I run all builds on the same slave then I have no issues. Tried it with all 3 slaves. If I run one build one each slave then I end up with connection timed out issues. Not sure why I have this

Re: Proposal: revisiting JUC in 2016

Taking off my cloudbees hat and putting on my old hat being based in Europe. Getting approval to attend conferences abroad (outside Europe) for me was not always easy - as it involves large travel and time lost due to this. As such it was easier to go to a european conference. I also feel

Re: Links in HTML Reports now working

Ah, I remember this from long time ago. The issue is that links cannot point to folders. They need to point to files in fodlers. If they only point to fodlers, Jetty will refuse to load them in this context. On Tuesday, 20 October 2015 11:30:17 UTC+1, Schalk Cronjé wrote: > > I was trying to

Re: Proposal: revisiting JUC in 2016

Hello James, (reply in line) 2015-10-20 12:03 GMT+02:00 James Nord : > Taking off my cloudbees hat and putting on my old hat being based in Europe. > > Getting approval to attend conferences abroad (outside Europe) for me was > not always easy - as it involves large travel

Re: Connection time out issues

On 20. okt. 2015 10:31, uscengin...@gmail.com wrote: > My setup: > master running on ubuntu > 3 x slaves running on OSX > > I am running 3 builds at one time. > When I run all builds on the same slave then I have no issues. Tried it > with all 3 slaves. > If I run one build one each slave then I

Links in HTML Reports now working

I was trying to track down this issue today on one site. The index page of the report of visible, but when clicking on any of the relative links in the landing page, Jetty such says Not Found. I am verified that all of the files is on disk and in a location which I would deem to be correct. (If

Re: Proposal: revisiting JUC in 2016

Wearing my family hat. Can we please have this at a time when I do not have to worry about school runs or I will never get approval to go ;-) "oh a three day party in CA near San Francisco? And you expect me to take AL to handle the school run?" flashbacks of Florida! On Tuesday 20 October

RE: Jenkins build failure console output

It appears that Perforce is building a workspace at /home/abigail/p4/projects// I suppose the workspace definition could include mapping some files to /var/lib/jenkins/workspace. What is your Perforce workspace definition? From: jenkinsci-users@googlegroups.com

Re: docker connectivity issue

Thanks Nicolas and Richard for your valuable inputs it's resolved. Regards Irfan On Mon, Oct 19, 2015 at 10:12 AM, Richard Bywater wrote: > You shouldn't be pointing it at Port 22 as that's the SSH port. You'll > need to check which tcp port you've got your Docker daemon

Jenkins nosetests FAILED

Hi, I have the next issue: During my nose testing I have one test failed and Cubertura report didn't created: --- Ran 155 tests in 37.580s FAILED (failures=1) Build step 'Execute shell' marked build as failure Skipping Cobertura coverage report as

Re: Jenkins nosetests FAILED

(replies inline) On Tue, 20 Oct 2015, Fedor Kompaniets wrote: > During my nose testing I have one test failed and Cubertura report didn't > created: > > --- > > > Ran 155 tests in 37.580s > > FAILED (failures=1) > Build step 'Execute shell' marked

Re: 1.634 not downloading zip archives on Windows

Known issue: https://issues.jenkins-ci.org/browse/JENKINS-31015 On 19.10.2015, at 18:38, Trinition wrote: > We just updated to 1.634 but our promotion jobs that start by downloading the > archived artifacts. That is failing because the download link itself is > returning

1.634 not downloading zip archives on Windows

We just updated to 1.634 but our promotion jobs that start by downloading the archived artifacts. That is failing because the download link itself is returning an HTTP 500. For example: http://jenkins/job/MyJob/1046/artifact/*zip*/archive.zip I get an "Oops!" evil Jenkins, and a stack trace

Re: Proposal: revisiting JUC in 2016

Yes, the downside of not having JUC in Europe has been considered. One of the problems we had in the past few years with JUC in Europe has been that we have never managed to create a truly pan-Europe event. When we do JUC in Paris, only French people came. Did one in Berlin and only Germans came.

Re: Proposal: revisiting JUC in 2016

@ James. majority of the JUC West attendees were from California: San Francisco, San Jose , Sunnyvale, Santa Clara, Mt View, and Palo Alto. For JUC EU - London had the most attendees. Cambridge, Berlin, Dublin came in second but each of these cities had single digit attendees. On Tuesday,

Re: Proposal: revisiting JUC in 2016

when JUC EU was planned - the goal has always been to find a central location where folks from diff parts of EU can conveniently attend. But it didn't turn out that way - mainly local people attended. And of course one big event in EU is very costly. The CB-Jenkins Summits will provide the

Re: Proposal: revisiting JUC in 2016

> On 20 Oct 2015, at 23:12, Alyssa wrote: > > when JUC EU was planned - the goal has always been to find a central location > where folks from diff parts of EU can conveniently attend. But it didn't turn > out that way - mainly local people attended. And of course one big

Re: Jenkins build failure console output

Hi, I switched to Perforce plugin from P4 Plugin from Perforce, and everything works fine. It seems the new P4 plugin is a lot harder to configure. Thank you. Martin On Tuesday, October 20, 2015 at 7:42:56 AM UTC-4, rginga wrote: > > It appears that Perforce is building a workspace at >

How to control access to the Jenkins build site?

For example, if my URL for the Jenkins service is: jenkins.mycompany.com:8080 Even without logging into this site, outsiders can still browse a lot of information of the build and the project. In particular through the Workspace, others can see pom.xml and can even download the whole project