Open olivierdagenais opened 1 year ago
I believe you have implemented properly conditions and actions. I think you don't need to create new BuildPosition because you can use https://github.com/jenkinsci/build-history-manager-plugin/blob/master/src/main/java/pl/damianszczepanik/jenkins/buildhistorymanager/model/conditions/MatchEveryBuildCondition.java#L12 and configure it so it is executed 15 times https://github.com/jenkinsci/build-history-manager-plugin/blob/master/src/main/java/pl/damianszczepanik/jenkins/buildhistorymanager/model/Rule.java#L31
What feature do you want to see added?
Given these requirements:
Is it possible to implement with the build-history-manager plugin?
Here are some examples/test scenarios:
It feels like we would need a
BuildPosition
condition, which compares against a monotonically-increasing counter of runs (assuming the latest run starts at 1), such that we would be able to craft the configuration to have the following rules:conditions: [BuildPosition(maxBuildPosition: 15)], continueAfterMatch: false
conditions: [BuildAgeRange(maxDaysAge: 10)], continueAfterMatch: false
actions: [DeleteBuild()]
What do you think?
Thanks!
Upstream changes
n/a