VMWare cloud agent starts before apply of customization specification
Hello!
I got into problem with cloud agents.
I have defined vmware customization specification and pointed teamcity to this specification.
But it seems like Teamcity authorizes agent before applying customization and build starts immediately after cloning vm from template. Such behaviour causes build failure since agent machine reboots after customization regardless of build process status.
Any solution here?
Please sign in to leave a comment.
Hi, customization spec is passed into VMware API call that creates VM. And it's only applied when TC creates a new VM, not start existing one.
Please check your setup or whether customization spec can be actually applied to the VM. TeamCity just uses VMware API.