jenkinsci / jenkinsci/release-plugin
[JENKINS-17579] Limit number of entries in "Previous release versions" section
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 24
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I was wondering if it's possible to limit the number of entries in the "Previous release versions" section when opening up a form in a release job. In our case we don't discard old builds and we're up to #2000 which means if we upgrade to the latest version of the plugin (we're stuck at version 1.10), the page takes ages to load as it adds a table for all 2000 historical releases. The build history on the left limits the list by default so something similar behaviour would be very nice.
Originally reported by kolos, imported from: Limit number of entries in "Previous release versions" section
- assignee:
petehayes
- status: Open
- priority: Major
- component(s): release-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251223-222157
Raw content of original issue
I was wondering if it's possible to limit the number of entries in the "Previous release versions" section when opening up a form in a release job. In our case we don't discard old builds and we're up to #2000 which means if we upgrade to the latest version of the plugin (we're stuck at version 1.10), the page takes ages to load as it adds a table for all 2000 historical releases. The build history on the left limits the list by default so something similar behaviour would be very nice.
- environment:
Latest Jenkins with a looooong history in release job.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the release-job form code that builds the "Previous release versions" section, then compare it with the build history list's default limiting behavior. The work is done when long release histories no longer render every historical entry and the form remains usable for jobs with thousands of releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100