![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
yossis
|
|
Components:
|
artifactory-plugin |
|
Created:
|
12/Nov/14 3:18 AM
|
|
Description:
|
I have a job that builds RPMs, but only produces a new RPM when a certain update is available, meaning 2/3 times the job runs, it does not produce a new artifact.
I am settings Jenkins to discard old builds when more than 5 exist.
The problem I have is this plugin will delete an existing RPM from artifactory if the build succeeds, whether or not a new RPM was uploaded. The effect of this is that if I go several days with any updates (hence new RPMs being produced), this plugin will delete all such RPMs from artifactory.
It would be nice if this plugin did not simply blindly follow Jenkins cleaning up builds, but actually ensure that if the number of build kept is 5, then it will actually keep this many artifacts in artifactory. Or simply, a setting which says 'if I didnt upload anything new to artifactory, dont delete anything from artifactory'.
|
|
Environment:
|
Jenkins ver. 1.565.1
Plugin version 2.2.4
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Foo Bar
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
