JFTR:
By using my personal user credentials everything started to work. So it
really seems to be a issue of my build user's access rights.
Thank you very much for the heads up!
Now I am trying to find out, why the start script is expecting the java
installation beyond the SLAVE_HOME instead of
We had these issue in the past ... and this is what we discovered:
1) VSphereNotFoundException is raised also in the case the user don't have
permission to see it.
So, considering you are 100% sure the name is correct, I can tell you that
it's a permission error.
2) I know it may seems strange .
Hi Gianluca,
OK, the log was a good idea, thank you very much!
There I found:
Started provisioning VC9BuildSlave97yt3vpya79krvglcpcgevei4 from vSphereCloud
with 1 executors. Remaining excess workload: 0
Apr 01, 2020 5:13:01 PM WARNING
org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1 cal
Hi,
we use vSphere cloud plugin and some hints to help you debug:
1) go to the Jenkins log and check any error there
Some errors we had in the past:
- typo in the node label and the clone never started
- clone started but it was failing due to permission errors in vSphere (the
user is not able to
