-
Improvement
-
Resolution: Duplicate
-
Major
-
None
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
- duplicates
-
JENKINS-35143 Delete Pipeline Multibranch sub projects
-
- Closed
-
- is related to
-
-
- Resolved
-
[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 |
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Jesse Glick [ jglick ] |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link |
New:
This issue duplicates |
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.
| Resolution | Original: Not A Defect [ 7 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Link |
New:
This issue is related to |
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.
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).