|
||||||||
|
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/groups/opt_out.
Hi,
If future decision is done to discard (e.g. to free blocked unnecessary resources) old builds indeed I would have expected that decision to "keep this build forever" is independend from setting "discard old builds".
I encountered that use case as well.
The work around described in description is unfortunately not acceptable in my case since behavior is unclear to end users. It is hard to make it pass quality gates in my scenario.
Suggestion seems to be to have the "keep this build forever" available independly from discard settings.
Additional suggestion is to have a hint included while displaying "keep this build forever" although discarding is completely turned off currently. Hint and marking the build is still valid then since current settings might change.
Regards and all the best, – Oliver