[
https://issues.jenkins-ci.org/browse/JENKINS-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159720#comment-159720
]
SCM/JIRA link daemon commented on JENKINS-12076:
------------------------------------------------
Code changed in jenkins
User: James Nord
Path:
src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java
src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly
src/main/webapp/help-projectConfig-help-numberOfReleaseBuildsToKeep.html
src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseActionTest.java
http://jenkins-ci.org/commit/m2release-plugin/82e9e2c2fbdae06a4d04700ed5cf0bdcea9c8ce8
Log:
[FIXED JENKINS-12076] Add the ability to specify the number of release builds
to keep.
If the number is -1 then all builds are kept.
a positive number will keep that many sucessfull release builds.
Any other number (< -1 or 0) will cause no release builds to be kept.
Compare: https://github.com/jenkinsci/m2release-plugin/compare/18712bd...82e9e2c
> m2 Release Plugin lock builds
> -----------------------------
>
> Key: JENKINS-12076
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12076
> Project: Jenkins
> Issue Type: New Feature
> Components: m2release
> Affects Versions: current
> Environment: Any
> Reporter: Terry Sposato
> Assignee: teilo
> Priority: Trivial
>
> Is it possible to have a configurable option per job to always keep a m2
> release build locked.
> At the moment only the latest release build stays locked...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
