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

GitHub Org Folders Discard Old Items settings do not seem to have any effect

    XMLWordPrintable

Details

    • 6.9

    Description

      See screenshot taken from ci.jenkins.io and its Plugins GitHub Org folder

      I double-checked and there are no properties being set by the Pipeline in the screenshot, so I would expect that the Discard Old Items I define in the Org Folder to actually apply

      Attachments

        Activity

          jglick Jesse Glick added a comment -

          The orphaned item strategy of the organization folder applies to, well, items. Thus, repository folders—if you delete a repository (or whatever), its folder will be cleaned up according to those settings. It also gets propagated to the orphaned item strategy for the repository folder, meaning that if you close a PR, the corresponding branch project will get deleted according to your settings.

          This has nothing whatsoever to do with discarding old builds. That is controlled by buildDiscarder properties in the Jenkinsfile. The UI should express the distinction more clearly.

          Separately, it would be useful to have a plugin which applies a system-wide or folder-wide mandatory build retention policy even to jobs which have a lax policy or none at all.

          jglick Jesse Glick added a comment - The orphaned item strategy of the organization folder applies to, well, items. Thus, repository folders—if you delete a repository (or whatever), its folder will be cleaned up according to those settings. It also gets propagated to the orphaned item strategy for the repository folder, meaning that if you close a PR, the corresponding branch project will get deleted according to your settings. This has nothing whatsoever to do with discarding old builds. That is controlled by buildDiscarder properties in the Jenkinsfile . The UI should express the distinction more clearly. Separately, it would be useful to have a plugin which applies a system-wide or folder-wide mandatory build retention policy even to jobs which have a lax policy or none at all.
          tavin Tavin Cole added a comment -

          Has such a plugin become available? Imo an override for this setting should be exposed by the github org folder configuration UI, without another plugin, but any solution would be welcome. Otherwise we have to modify dozens of Jenkinsfiles.

          tavin Tavin Cole added a comment - Has such a plugin become available? Imo an override for this setting should be exposed by the github org folder configuration UI, without another plugin, but any solution would be welcome. Otherwise we have to modify dozens of Jenkinsfiles.

          People

            rsandell rsandell
            rtyler R. Tyler Croy
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: