[weld-builds] Build failed in Jenkins: Weld-2.x-incontainer-WF8-osprey #9

ci-builds at redhat.com ci-builds at redhat.com
Mon Aug 4 15:43:00 EDT 2014


See <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-incontainer-WF8-osprey/9/>

------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on osprey-03 in workspace <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-incontainer-WF8-osprey/ws/>
Checkout:Weld-2.x-incontainer-WF8-osprey / <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Weld-2.x-incontainer-WF8-osprey/ws/> - hudson.remoting.Channel at 6518c7e5:osprey-03
Using strategy: Default
Last Built Revision: Revision 4de3cc18422eb7121c05b4d26ac41abd4358fa23 (origin/master)
Cloning the remote Git repository
Cloning repository git://github.com/weld/core.git
git --version
git version 1.8.3.1
Fetching upstream changes from origin
Commencing build of Revision 4de3cc18422eb7121c05b4d26ac41abd4358fa23 (origin/master)
Checking out Revision 4de3cc18422eb7121c05b4d26ac41abd4358fa23 (origin/master)
[Weld-2.x-incontainer-WF8-osprey] $ bash -xe /tmp/hudson890109498590363844.sh
+ source /mnt/osprey-share/weld/common-osprey.sh
/tmp/hudson890109498590363844.sh: line 2: /mnt/osprey-share/weld/common-osprey.sh: No such file or directory
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results


More information about the weld-builds mailing list