[JENKINS-69341] Text and logo exceed sidepanel in "About Jenkins" view

[frankie139506]

See JENKINS-69341.

Proposed changelog entries

• Too minor.

Proposed upgrade guidelines

N/A

Submitter checklist

• (If applicable) Jira issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• Appropriate autotests or explanation to why this change has no tests
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadoc, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO") if applicable.
• New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content-Security-Policy directives (see documentation on jenkins.io).
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

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

• There are at least 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 does not block the change
• Changelog entries in the PR 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, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (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).

[NotMyFault]

Thanks for addressing, looks much better:

[daniel-beck]

I don't think changing the sidepanel width for all pages in Jenkins is an appropriate solution when one page in Jenkins with a completely custom layout looks slightly awkward in incremental builds only.

If the sidepanel should be made wider to accommodate a real need of wider labels, that's fine. But this isn't it.

Notably, the About page layout is broken at window widths of 970-1165 px anyway, so it's not even that that particular page's layout is fine otherwise.

[frankie139506]

I don't think changing the sidepanel width for all pages in Jenkins is an appropriate solution when one page in Jenkins with a completely custom layout looks slightly awkward in incremental builds only.

If the sidepanel should be made wider to accommodate a real need of wider labels, that's fine. But this isn't it.

Notably, the About page layout is broken at window widths of 970-1165 px anyway, so it's not even that that particular page's layout is fine otherwise.

@daniel-beck Do you mean that I need an underlaying fix?

[daniel-beck]

Do you mean that I need an underlaying fix?

No, I mean that this fix changes too much (every page in Jenkins) for a very narrow bug (incremental version numbers are larger than the sidepanel on the About Jenkins page).

Perhaps look into whether the About Jenkins sidepanel can be set up to wrap overflowing text?

[frankie139506]

Do you mean that I need an underlaying fix?

No, I mean that this fix changes too much (every page in Jenkins) for a very narrow bug (incremental version numbers are larger than the sidepanel on the About Jenkins page).

Perhaps look into whether the About Jenkins sidepanel can be set up to wrap overflowing text?

@daniel-beck I have made some change. Please take a look.

[daniel-beck]

Looks reasonable now (screenshot with patched DOM):

[frankie139506]

Looks reasonable now (screenshot with patched DOM):

Thanks. If have any problem plz tell me.

obsolete

[NotMyFault]

Thanks for addressing the outstanding concerns!

---

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!

[github-actions]

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