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

Nodes do not restart with pipeline jobs

XMLWordPrintable

      Description

      We use the vsphere nodes to execute our tests. We need the environment to be clean at the start of every test run, so we use the 'shutdown and revert' option in conjunction with the 'limited jobs' option to revert the virtual machines to a clean state.

      We would like move our job config out of Jenkins and into the project repo by using Pipelines and Jenkinsfiles.

      However, the nodes do not power down and revert once a pipeline job is finished, and instead only restart once a normal freestyle job has completed.

      Steps To Reproduce

      1. Configure a vsphere node to shutdown and revert once a job has finished
      2. Execute a pipeline job on this node

      Expected Results

      2. node powers off and reverts

      Actual Results

      2. Node remains online, and new jobs are executed with the dirty state.

          [JENKINS-38930] Nodes do not restart with pipeline jobs

          David Terry created issue -
          David Terry made changes -
          Description Original: **Description**

          We use the vsphere nodes to execute our tests. We need the environment to be clean at the start of every test run, so we use the 'shutdown and revert' option in conjunction with the 'limited jobs' option to revert the virtual machines to a clean state.

          We would like move our job config out of Jenkins and into the project repo by using Pipelines and Jenkinsfiles.

          However, the nodes do not power down and revert once a pipeline job is finished, and instead only restart once a normal freestyle job has completed.

          **Steps To Reproduce**

          1. Configure a vsphere node to shutdown and revert once a job has finished
          2. Execute a pipeline job on this node

          **Expected Results**

          2. node powers off and reverts

          **Actual Results**

          2. Node remains online, and new jobs are executed with the dirty state.           		New: *Description*

          We use the vsphere nodes to execute our tests. We need the environment to be clean at the start of every test run, so we use the 'shutdown and revert' option in conjunction with the 'limited jobs' option to revert the virtual machines to a clean state.

          We would like move our job config out of Jenkins and into the project repo by using Pipelines and Jenkinsfiles.

          However, the nodes do not power down and revert once a pipeline job is finished, and instead only restart once a normal freestyle job has completed.

          *Steps To Reproduce*

          1. Configure a vsphere node to shutdown and revert once a job has finished
          2. Execute a pipeline job on this node

          *Expected Results*

          2. node powers off and reverts

          *Actual Results*

          2. Node remains online, and new jobs are executed with the dirty state.
          Michel Lawaty made changes -
          Assignee New: Michel Lawaty [ michel117 ]
          Michel Lawaty made changes -
          Assignee Original: Michel Lawaty [ michel117 ]
          Jesse Glick made changes -
          Labels New: pipeline
          Jesse Glick made changes -
          Remote Link New: This issue links to "Dev guide (Web Link)" [ 15604 ]

            Unassigned Unassigned
            david_terry David Terry
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: