Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display a notice when there are plugins installed or updates available #8208

Merged
merged 20 commits into from Aug 15, 2023

Conversation

janfaracik
Copy link
Contributor

@janfaracik janfaracik commented Jun 29, 2023

Followup to #8186. Adds a notice to the Installed plugins page(s) as well as to the updates page to tell the user when there are no plugins installed/updates available, this is rather than displaying the table. Also disables the search bar.

image image image

Testing done

  • Notice shows when no plugins are installed
  • Notice hides when plugins are installed
  • Notice shows when no updates are available
  • Notice hides when updates are available

Proposed changelog entries

  • Display a notice when plugin updates are available or when there are no plugins installed.

Proposed upgrade guidelines

N/A

Submitter checklist

Edit tasklist title
Beta Give feedback Tasklist Submitter checklist, more options

Delete tasklist

Delete tasklist block?
Are you sure? All relationships in this tasklist will be removed.
  1. The Jira issue, if it exists, is well-described.
    Options
  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.
    Options
  3. There is automated testing or an explanation as to why this change has no tests.
    Options
  4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
    Options
  5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
    Options
  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).
    Options
  7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
    Options
  8. For new APIs and extension points, there is a link to at least one consumer.
    Options

Desired reviewers

@jenkinsci/sig-ux

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

Maintainer checklist

Edit tasklist title
Beta Give feedback Tasklist Maintainer checklist, more options

Delete tasklist

Delete tasklist block?
Are you sure? All relationships in this tasklist will be removed.
  1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
    Options
  2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
    Options
  3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
    Options
  4. Proper changelog labels are set so that the changelog can be generated automatically.
    Options
  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).
    Options
  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).
    Options

@NotMyFault NotMyFault 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 Jun 30, 2023
Copy link
Member

@NotMyFault NotMyFault left a comment

Choose a reason for hiding this comment

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

Tests will need a few fixes too, as it seems

core/src/main/resources/hudson/PluginManager/updates.jelly Outdated Show resolved Hide resolved
@NotMyFault NotMyFault added needs-ath-build Needs to run through the full acceptance-test-harness suite needs-test-fix One or more test case(s) need to be updated labels Jun 30, 2023
Copy link
Contributor

@yaroslavafenkin yaroslavafenkin left a comment

Choose a reason for hiding this comment

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

Looks fine security wise

@yaroslavafenkin yaroslavafenkin added the security-approved @jenkinsci/core-security-review reviewed this PR for security issues label Jul 4, 2023
@janfaracik janfaracik changed the title Display a notice when there are no updates available Display a notice when there are plugins installed or updates available Jul 8, 2023
@janfaracik
Copy link
Contributor Author

I've updated this to include the Installed plugins page(s) which had slipped my mind before, and I've also removed the usage of :has() as it was breaking the tests (for the time being). Rereviews and another security look over would be appreciated. Thanks

@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Jul 10, 2023
@github-actions
Copy link

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 Jul 10, 2023
@NotMyFault NotMyFault removed the needs-test-fix One or more test case(s) need to be updated label Jul 17, 2023
@NotMyFault NotMyFault removed the request for review from yaroslavafenkin July 17, 2023 21:53
@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Jul 27, 2023
@github-actions
Copy link

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 Jul 27, 2023
@daniel-beck
Copy link
Member

For UI change PRs in general, it would be useful to have both "before" and "after" screenshots (not just "after"). For example,

this

Screenshot 2023-07-27 at 10 46 12
is what the plugin manager currently looks like. While the suggested change does look better, the title and description of this PR are misleading. In all three cases, a message is already shown, there's not just a table header.

timja added a commit to jenkinsci/acceptance-test-harness that referenced this pull request Aug 12, 2023
@timja timja added ath-successful This PR has successfully passed the full acceptance-test-harness suite and removed needs-ath-build Needs to run through the full acceptance-test-harness suite labels Aug 13, 2023
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.

Looks really nice

@timja timja requested review from a team and NotMyFault and removed request for NotMyFault August 14, 2023 07:51
Copy link
Member

@NotMyFault NotMyFault left a comment

Choose a reason for hiding this comment

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

This looks nice!

@timja
Copy link
Member

timja commented Aug 14, 2023

/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 Aug 14, 2023
@timja timja merged commit 83085ba into jenkinsci:master Aug 15, 2023
18 checks passed
@timja timja deleted the no-updates-notice branch August 15, 2023 14:38
yaroslavafenkin pushed a commit to yaroslavafenkin/jenkins that referenced this pull request Sep 26, 2023
jenkinsci#8208)

Co-authored-by: Alexander Brandes <brandes.alexander@web.de>
Co-authored-by: Alexander Brandes <mc.cache@web.de>
Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ath-successful This PR has successfully passed the full acceptance-test-harness suite 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 security-approved @jenkinsci/core-security-review reviewed this PR for security issues web-ui The PR includes WebUI changes which may need special expertise
Projects
None yet
5 participants