Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50262

Plugin doesn't wait for sandbox to complete before returning

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor 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

          [JENKINS-50262] Plugin doesn't wait for sandbox to complete before returning

          Tomer Admon added a comment -

          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

          Tomer Admon added a comment - 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

          jim woodlock added a comment -

          I've added the environment info, along with a couple of screen shots.  Basically the Jenkins shot shows the job has moved onto the next step, but the cloudshell shot shows the blueprint is still in setup.   This is a similar problem we ran into with our Robot Framework to CloudShell integration - there was a second check required to know when a blueprint completes, we only had the first check and were doing a similar thing there (moving on to early)

          jim woodlock added a comment - I've added the environment info, along with a couple of screen shots.  Basically the Jenkins shot shows the job has moved onto the next step, but the cloudshell shot shows the blueprint is still in setup.   This is a similar problem we ran into with our Robot Framework to CloudShell integration - there was a second check required to know when a blueprint completes, we only had the first check and were doing a similar thing there (moving on to early)

          Tomer Admon added a comment -

          Thanks jimw ,

          Please open this as a support request in Quali's support http://support.quali.com and we will handle this with you.

          Tomer

          Tomer Admon added a comment - Thanks jimw , Please open this as a support request in Quali's support  http://support.quali.com  and we will handle this with you. Tomer

            tomeradmon Tomer Admon
            jimw jim woodlock
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: