See <https://jclouds.ci.cloudbees.com/job/jclouds-labs/303/changes>

Changes:

[Andrew Bayer] JCLOUDS-381. Allow explicit naming of nodes, decouple group 
identity from node name

------------------------------------------
Started by an SCM change
Building remotely on 28e36430 in workspace 
<https://jclouds.ci.cloudbees.com/job/jclouds-labs/ws/>
Checkout:jclouds-labs / <https://jclouds.ci.cloudbees.com/job/jclouds-labs/ws/> 
- hudson.remoting.Channel@2a0a1891:28e36430
Using strategy: Default
Last Built Revision: Revision cd56d135cc653a133969adf147d3bc42cc204b66 
(origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision 1804f2b6b4c2672135ecc349ed97f52cffc5267c 
(origin/master)
Checking out Revision 1804f2b6b4c2672135ecc349ed97f52cffc5267c (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.

Reply via email to