Skip to content

Add experimental Plugin Manager UI#11332

Merged
timja merged 14 commits intojenkinsci:masterfrom
janfaracik:add-experimental-plugin-manager
Feb 18, 2026
Merged

Add experimental Plugin Manager UI#11332
timja merged 14 commits intojenkinsci:masterfrom
janfaracik:add-experimental-plugin-manager

Conversation

@janfaracik
Copy link
Member

@janfaracik janfaracik commented Nov 23, 2025

This PR adds support for the new experimental Manage Jenkins UI for Plugins and its subpages.

Screenshots

Screenshot 2025-11-23 at 08 19 03
More screenshots Screenshot 2025-11-23 at 08 19 14 Screenshot 2025-11-23 at 08 19 20 Screenshot 2025-11-23 at 08 19 25 Screenshot 2025-11-23 at 08 19 31

Changes

  • A new section has been added to Manage Jenkins, titled Plugins
  • There's three new entries: 'Updates', 'Available', 'Installed'
  • 'Advanced settings' has been moved to an overflow - would be good to get thoughts on this, my thinking is the label/icon is a little too generic and might confuse people by being top level
  • 'Download progress' shows when there are downloads

Testing done

  • UI works as expected
  • There should be no regressions when the Experimental Manage Jenkins flag is off

Proposed changelog entries

  • Add experimental Plugin Manager UI

Proposed changelog category

/label web-ui,rfe

Proposed upgrade guidelines

N/A

Submitter checklist

  • The Jira issue, if it exists, is well-described.
  • 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.
  • There is automated testing or an explanation as to why this change has no tests.
  • New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
  • New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
  • UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, 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).
  • For dependency updates, there are links to external changelogs and, if possible, full differentials.
  • For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/sig-ux

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

Maintainer checklist

  • There are at least two (2) approvals for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
  • Proper changelog labels are set so that the changelog can be generated automatically.
  • 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).
  • 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).

@comment-ops-bot comment-ops-bot bot added web-ui The PR includes WebUI changes which may need special expertise rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted labels Nov 23, 2025
@janfaracik janfaracik added the squash-merge-me Unclean or useless commit history, should be merged only with squash-merge label Nov 23, 2025
@janfaracik janfaracik requested a review from a team November 23, 2025 08:20
}, 5000);
}

window.scrollTo(0, 10000);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This results in weird scrolling behaviour every time the page loads, don't see a great reason to keep it for either legacy/experimental view.

<j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:l="/lib/layout"
xmlns:t="/lib/hudson" xmlns:f="/lib/form">
<l:layout title="${%Advanced settings} - ${%Plugins}" permission="${app.SYSTEM_READ}">
<l:settings-subpage permission="${app.SYSTEM_READ}" header="${null}" includeSidepanel="true">
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend ignoring whitespace when reviewing this.

@janfaracik janfaracik marked this pull request as ready for review November 23, 2025 10:19
Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've given this a good test, nothing major

feedback below, looks great though

@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Dec 19, 2025
@github-actions
Copy link
Contributor

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot removed the unresolved-merge-conflict There is a merge conflict with the target branch. label Jan 22, 2026
Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Advanced settings appear to be cut-off on all plugin manager pages:

image

Using 27" monitor

@timja
Copy link
Member

timja commented Jan 24, 2026

Advanced settings should probably have a breadcrumb?

image

@timja
Copy link
Member

timja commented Jan 24, 2026

Advanced settings should probably have a breadcrumb?

image

All of them could probably do with it tbh

@janfaracik janfaracik requested a review from timja January 27, 2026 10:57
Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, breadcrumb can come later

@timja timja requested a review from a team January 27, 2026 13:28
@janfaracik
Copy link
Member Author

Hey @mawinter69, any thoughts on this?

Copy link
Contributor

@mawinter69 mawinter69 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@timja
Copy link
Member

timja commented Feb 18, 2026

/label ready-for-merge


This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

@comment-ops-bot comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Feb 18, 2026
@timja timja added this pull request to the merge queue Feb 18, 2026
Merged via the queue into jenkinsci:master with commit a738e5e Feb 18, 2026
18 checks passed
@timja timja deleted the add-experimental-plugin-manager branch February 18, 2026 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted squash-merge-me Unclean or useless commit history, should be merged only with squash-merge web-ui The PR includes WebUI changes which may need special expertise

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants