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

Deleting a project does not stop all running builds

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • Jenkins 1.642.1
      Pipeline 1.13

      Current behaviour:
      1. A Multibranch Pipeline project is running a build.
      2. Delete that project.
      3. Builds, flyweight and heavyweight, are still running
      4. Attempting to stop the builds manually, by clicking the stop icon in the 'Build executor status', results in no visible effect.

      Expected behaviour:
      1. A Multibranch Pipeline project is running a build.
      2. Delete that project.
      3. Builds, flyweight and heavyweight, have been stopped.

          [JENKINS-32783] Deleting a project does not stop all running builds

          Zach Norris created issue -
          Zach Norris made changes -
          Summary Original: Removing a Multibranch Pipeline project does not stop its running jobs New: Removing a Multibranch Pipeline project does not stop its running build
          Zach Norris made changes -
          Description Original: Current behaviour:
          1. A Multibranch Pipeline project is running a job.
          2. Delete that project.
          3. Jobs, flyweight and heavyweight, are still running

          Expected behaviour:
          1. A Multibranch Pipeline project is running a job.
          2. Delete that project.
          3. Jobs, flyweight and heavyweight, have been stopped.
          New: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          Zach Norris made changes -
          Description Original: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          New: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running
          4. Attempting to stop the builds manually

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          Zach Norris made changes -
          Description Original: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running
          4. Attempting to stop the builds manually

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          New: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running
          4. Attempting to stop the builds manually, by clicking the stop icon in the 'Build executor status', results in no visible effect.

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          Jesse Glick made changes -
          Summary Original: Removing a Multibranch Pipeline project does not stop its running build New: Deleting a Pipeline project does not stop its running build
          Zach Norris made changes -
          Description Original: Current behaviour:
          1. A Multibranch Pipeline project is running a buld.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running
          4. Attempting to stop the builds manually, by clicking the stop icon in the 'Build executor status', results in no visible effect.

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          New: Current behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, are still running
          4. Attempting to stop the builds manually, by clicking the stop icon in the 'Build executor status', results in no visible effect.

          Expected behaviour:
          1. A Multibranch Pipeline project is running a build.
          2. Delete that project.
          3. Builds, flyweight and heavyweight, have been stopped.
          Jesse Glick made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: workflow-plugin [ 18820 ]
          Assignee Original: Jesse Glick [ jglick ]
          Labels New: workflow
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Summary Original: Deleting a Pipeline project does not stop its running build New: Deleting a project does not stop all running builds
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-25240 [ JENKINS-25240 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 168448 ] New: JNJira + In-Review [ 183134 ]
          Andrew Bayer made changes -
          Labels Original: workflow New: pipeline workflow

            Unassigned Unassigned
            znorris Zach Norris
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: