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 the system JAVA_HOME but I
guess I will make that by myself...
Am Mittwoch, 1. April 2020 17:13:45 UTC+2 schrieb Christoph Fetzer:
>
> Hi,
>
> I have access to an Esxi-Server used by a vSphere instance. I set up a
> vsphere cloud in my Jenkins installation properly ("Test connection" works).
> I set up a template VM (Windows 10) with a Snapshot, Autologon and
> Autostart according to
> https://github.com/jenkinsci/vsphere-cloud-plugin/blob/master/docs/vm-configuration.md
> I configured a startup template in the vSphere cloud according to:
> https://github.com/jenkinsci/vsphere-cloud-plugin/blob/master/docs/jenkins-configuration.md
> I'd like to use the approch "Static configuration" mentioned for startup
> of the nodes.
> In the vSphere cloud I made the plugin use "VC9-build" als label for the
> nodes.
> Then I changed a build job based on that Jenkinsfile (declarative):
>
> #!groovy
> pipeline {
> agent {
> label 'VC9-build'
> }
> ...
> }
>
>
> My expectation is that after start of the job the vsphere plugin would
> clone a VM in ESXI, start that up, connect it to jenkins and make the job
> run there.
> Instead I only have a job in may waiting queue with the name "part of
> ${jobname}" and I can't see anything on vSpere so I guess clone of the
> machine didn't even start.
> Am I missing a link somewhere in to make the node creation start?
>
> BR,
> Christoph
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/a1d0cd28-551b-43b4-80ad-70dc8b6a47d2%40googlegroups.com.
