-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins v2.111, CloudShell plugin 1.6.3, CloudShell v8.2
It appears that the plugin isn't checking the state of the sandbox before returning. We see it initiate the sandbox but then it immediately returns to Jenkins and the next build step executed. Meanwhile on CloudShell the blueprint shows as still in the Setup execution phase. The plugin should wait (or at least have a option to wait) for the blueprint to complete; if the next step in the Jenkins build is to process output it might have incomplete data if the blueprint hasn't finished
Hi jimw
Can you please add the plugin version you are using and an example of how you are using it? is it a pipeline script or a freestyle project? Can you share the output from the build console?
By default, the plugin will start a sandbox and will wait for it to be in "Active" state so the Jenkins job will be able to use the sandbox.
We usually handle this kind of tickets thought out Zendesk support portal, please open a ticket there and our support guys will be able to debug and help you solve the issue.
Thanks,
Tomer