• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • branch-api-plugin
    • None

      Right now it seems not possible tho delete a pipeline project that is part of a multibranch pipeline project. There is no UI element to do it and appending /delete to the project url results in missing userrights for "Job/Delete".

          [JENKINS-35143] Delete Pipeline Multibranch sub projects

          Martin Heinzerling created issue -
          Martin Heinzerling made changes -
          Link New: This issue is related to JENKINS-35144 [ JENKINS-35144 ]

          Oleg Nenashev added a comment -

          It's not related to the core

          Oleg Nenashev added a comment - It's not related to the core
          Oleg Nenashev made changes -
          Summary Original: Delete Multibranch sub projects New: Delete Pipeline Multibranch sub projects
          Oleg Nenashev made changes -
          Component/s New: workflow-multibranch-plugin [ 21465 ]
          Component/s Original: core [ 15593 ]
          Oleg Nenashev made changes -
          Assignee New: Manuel Recena Soto [ recena ]

          Jesse Glick added a comment -

          As designed. This is a computed folder, so the contents are inferred from an external source of truth.

          It has been suggested that if your orphaned item strategy is configured to leave orphaned children undeleted for some time, you should have the option to delete a particular orphan eagerly.

          Deleting a non-orphaned child makes no sense, as it would simply be recreated with the next branch indexing.

          Jesse Glick added a comment - As designed. This is a computed folder, so the contents are inferred from an external source of truth. It has been suggested that if your orphaned item strategy is configured to leave orphaned children undeleted for some time, you should have the option to delete a particular orphan eagerly. Deleting a non-orphaned child makes no sense, as it would simply be recreated with the next branch indexing.

          Martin Heinzerling added a comment - - edited

          Maybe we also need a more sophisticated orphaned item strategy, just thinking of small feature branches vs. release branches which might have a different live time as a Jenkins project. An integrated feature branch might be dropped after 7-14 days, but a release branch after 3 releases which might be 6-8 weeks etc.

          Deleting a non-orphaned child makes no sense, as it would simply be recreated with the next branch indexing.

          It might make sense, if you are experimenting with the build/pipeline setup and want to drop the first 30 failing builds in your project to get nicer plots etc.

          Martin Heinzerling added a comment - - edited Maybe we also need a more sophisticated orphaned item strategy, just thinking of small feature branches vs. release branches which might have a different live time as a Jenkins project. An integrated feature branch might be dropped after 7-14 days, but a release branch after 3 releases which might be 6-8 weeks etc. Deleting a non-orphaned child makes no sense, as it would simply be recreated with the next branch indexing. It might make sense, if you are experimenting with the build/pipeline setup and want to drop the first 30 failing builds in your project to get nicer plots etc.
          Manuel Recena Soto made changes -
          Link New: This issue is duplicated by JENKINS-35251 [ JENKINS-35251 ]
          Jesse Glick made changes -
          Component/s New: branch-api-plugin [ 18621 ]
          Component/s Original: workflow-multibranch-plugin [ 21465 ]

            recena Manuel Recena Soto
            mheinzerling Martin Heinzerling
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: