You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by je...@cloudbees.com on 2013/11/26 20:02:13 UTC
Build failed in Jenkins: jclouds-chef #675
See <https://jclouds.ci.cloudbees.com/job/jclouds-chef/675/>
------------------------------------------
Started by upstream project "jclouds" build number 2404
originally caused by:
Started by an SCM change
Building remotely on 7c8431a7 in workspace <https://jclouds.ci.cloudbees.com/job/jclouds-chef/ws/>
Checkout:jclouds-chef / <https://jclouds.ci.cloudbees.com/job/jclouds-chef/ws/> - hudson.remoting.Channel@42dc4279:7c8431a7
Using strategy: Default
Last Built Revision: Revision 7e6c6534ada1e11aad3376c3f43f4134153c256b (origin/master)
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/jclouds-chef.git
git --version
git version 1.7.11.7
Fetching upstream changes from origin
Commencing build of Revision 7e6c6534ada1e11aad3376c3f43f4134153c256b (origin/master)
Checking out Revision 7e6c6534ada1e11aad3376c3f43f4134153c256b (origin/master)
Parsing POMs
ERROR: No such settings file /private/jclouds/settings.xml exists
Please verify that your alternate settings file is specified properly and exists in the workspace.
Jenkins build is back to normal : jclouds-chef #676
Posted by je...@cloudbees.com.
See <https://jclouds.ci.cloudbees.com/job/jclouds-chef/676/>