JENKINS-68822 added support for removing all builds with LogRotator

[madisparn]

See JENKINS-68822.

Testing done

Verified configuration in UI
Checked that old configuration is loaded from disk
Run the unit tests

Proposed changelog entries

• Allow all builds to be removed by the build discarder.

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[timja]

hmm I think this logic may not be 100% correct.

I have selected "Remove last stable build" - Yes

and then I have a stable build (success) and 2 failures.

My stable build never gets removed because I have set Remove last successful build - no.

The UI seems to be a bit too tied to the implementation.

At a minimum I think if remove last stable build is selected as yes and the last successful build is a stable build then it should be removed.

---

I wonder if we need both UI options, would it be enough to just add the stable option?

Or do you have any ideas on how it could be simpler?

[madisparn]

Indeed, having a single UI setting is simpler.

[timja]

what about these? The label seems too tied to the developer writing code instead of from a user perspective imo.

Suggested change

	<f:entry title="${%Remove last stable and successful builds}"
	<f:entry title="${%Remove last build}"

or

Suggested change

	<f:entry title="${%Remove last stable and successful builds}"
	<f:entry title="${%Remove last successful build}"

successful is still a bit confusing as 'unstable' is successful from my reading of the code.

[madisparn]

Picked the shorter option, more clear to me as developer :)

[timja]

Thanks!

[daniel-beck]

Weak -0.5 as this does not appear to be a common use case and is better off being done in a plugin.

[NotMyFault]

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!

[welcome]

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.