Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
-
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
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | GitHub Org Folders Discard Old Items settings seem to have any effect | GitHub Org Folders Discard Old Items settings do not seem to have any effect |
| Component/s | branch-api-plugin [ 18621 ] | |
| Component/s | pipeline [ 21692 ] | |
| Labels | ux |
| Labels | ux | triaged-2018-11 ux |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Remote Link | This issue links to "branch-api-plugin PR #157 (Web Link)" [ 23057 ] |
| Remote Link | This issue links to "cloudbees-folder-plugin PR #128 (Web Link)" [ 23058 ] |
| Assignee | rsandell [ rsandell ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Fixed but Unreleased [ 10203 ] |
| Released As | 6.9 | |
| Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
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 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.
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.