jenkinsci / jenkinsci/matrix-project-plugin
[JENKINS-58663] Keep Forever Not Propogated to child builds
- Dominant language
- Java
- Stars
- 17
- Forks
- 85
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 5
Description
I have confirmed this behavior in 1.13. When marking the parent job as keep forever this dose not propagate to the child jobs. This is a critical issue for me due to the fact that the artifacts are archived in the child jobs and there is no way to arrogate them into the parent. This means there is currently no way to automate keeping the artifacts forever.
---
Originally reported by cdecke04, imported from: Keep Forever Not Propogated to child builds
kohsuke
Raw content of original issue
I have confirmed this behavior in 1.13. When marking the parent job as keep forever this dose not propagate to the child jobs. This is a critical issue for me due to the fact that the artifacts are archived in the child jobs and there is no way to arrogate them into the parent. This means there is currently no way to automate keeping the artifacts forever.
Contributor guide
Research direction
Start by reading the matrix-project-plugin code responsible for parent and child build retention, then reproduce the behavior described for Jenkins 1.13. Done means marking a parent job Keep Forever also preserves its child builds and archived artifacts; verify the result with a regression test if the project provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100