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

Provide different strategies for repositories and branches / pull request

      Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/branches/pr are never discarded.

      Discussed solutions would be to either:

      • Add the option to Delete items regardless of the Discard Policy
      • Adapt/re-think the Orphaned Item Strategy
      • Provide another Strategy

          [JENKINS-35251] Provide different strategies for repositories and branches / pull request

          Allan BURDAJEWICZ created issue -
          Allan BURDAJEWICZ made changes -
          Description Original: Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/branchs/pr are never discarded.

          Discussed solutions would be to either:

          * Adapt/re-think the Orphaned Item Strategy
          * Add the option to Delete items
          * Provide another Strategy
          New: Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/branches/pr are never discarded.

          Discussed solutions would be to either:

          * Add the option to Delete items regardless of the Discard Policy
          * Adapt/re-think the Orphaned Item Strategy
          * Provide another Strategy

          Jesse Glick added a comment -

          As designed. Children of computed folders are intentionally read-only. If you want them to go away after some time, you use an orphaned item strategy. If you want them to go away immediately, delete the repository (or at least its Jenkinsfile on all open branches).

          Jesse Glick added a comment - As designed. Children of computed folders are intentionally read-only. If you want them to go away after some time, you use an orphaned item strategy. If you want them to go away immediately, delete the repository (or at least its Jenkinsfile on all open branches).
          Jesse Glick made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ] New: Jesse Glick [ jglick ]
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Manuel Recena Soto made changes -
          Link New: This issue duplicates JENKINS-35143 [ JENKINS-35143 ]

          jglick What is the alternative?

          Manuel Recena Soto added a comment - jglick What is the alternative?

          Sorin Sbarnea added a comment -

          Sorry but this bug was closed without giving an explanation for the reported problem.
          Currently, the list of sub-projects (branches) is growing indefinitely and we were not able to find any option for removal of the old ones.

          Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them and now we have hundreds of them for each repository.

          Sorin Sbarnea added a comment - Sorry but this bug was closed without giving an explanation for the reported problem. Currently, the list of sub-projects (branches) is growing indefinitely and we were not able to find any option for removal of the old ones. Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them and now we have hundreds of them for each repository.
          Sorin Sbarnea made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Sorin Sbarnea made changes -
          Link New: This issue is related to JENKINS-33819 [ JENKINS-33819 ]

          Jesse Glick added a comment -

          Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them

          If you are deleting the branches, and the orphaned item strategy is configured to delete old children, then the Jenkins projects should get deleted accordingly. If you see differently, please provide detailed steps to reproduce from scratch.

          Jesse Glick added a comment - Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them If you are deleting the branches, and the orphaned item strategy is configured to delete old children, then the Jenkins projects should get deleted accordingly. If you see differently, please provide detailed steps to reproduce from scratch.

            jglick Jesse Glick
            allan_burdajewicz Allan BURDAJEWICZ
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: