[JENKINS-43786] Overhaul of Manage Jenkins page#2857
[JENKINS-43786] Overhaul of Manage Jenkins page#2857oleg-nenashev merged 33 commits intojenkinsci:masterfrom
Conversation
| <st:include page="downgrade.jelly" /> | ||
|
|
||
| <table style="padding-left: 2em;" id="management-links"> | ||
| <style type="text/css"> |
There was a problem hiding this comment.
The final definition will be placed on the proper CSS file.
| </j:forEach> | ||
|
|
||
|
|
||
| <table style="padding-left: 2em; display: none;" id="management-links"> |
There was a problem hiding this comment.
It will be removed. It is still here for testing purposes.
There was a problem hiding this comment.
Given this block of code will be removed, this functional test needs to reviewed.
|
Do we need ATH runs for this? |
|
@daniel-beck WiP |
|
@recena What do you mean? I'm aware.
|
|
I do not think ATH has much of a coverage for this few things this can possibly break. |
|
Please provide before and after screenshot if it visible UI change. |
|
FWIW I like the "hover" design in the screenshot a lot. Ideally we'd make this a reusable component, so e.g. lists like new agent/view could use the same design. |
|
@KostyaSha I'll do it. To be honest, this is a basic re-style but IMHO improves some small details. Thanks for your participation. |
|
@daniel-beck Let me finish the approach and then, we can see the level of re-utilization. |
|
|
||
| SystemLogLink.DisplayName=System Log | ||
| SystemLogLink.Description=System log captures output from <tt>java.util.logging</tt> output related to Jenkins. | ||
| SystemLogLink.Description=System log captures output from <code>java.util.logging</code> output related to Jenkins. |
There was a problem hiding this comment.
Unrelated but <tt> is a obsolete element. Oldschool 😄
| <j:set var="_href" value="${href}"/> | ||
| <t:summary icon="${icon}" | ||
| href="${requiresConfirmation || post ? null : href}" iconOnly="true"> | ||
| <t:summary icon="${icon}" href="${requiresConfirmation || post ? null : href}" iconOnly="true"> |
| <j:set var="icon" value="${m.iconClassName != null ? m.iconClassName : m.iconFileName}"/> | ||
| <j:if test="${icon!=null}"> | ||
| <local:feature icon="${icon}" href="${m.urlName}" title="${m.displayName}" requiresConfirmation="${m.requiresConfirmation}" post="${m.requiresPOST}"> | ||
| <local:feature icon="${icon}" href="${m.urlName}" title="${m.displayName}" requiresConfirmation="${m.requiresConfirmation}" post="${m.requiresPOST}"> |
There was a problem hiding this comment.
@daniel-beck Do you know any case where <local:feature> is involved? I'd like to include this part in this re-style. Thanks.
There was a problem hiding this comment.
@oleg-nenashev And you? Could you help me?
There was a problem hiding this comment.
@recena local:feature is a local taglib defined directly in manage.jelly. https://github.com/recena/jenkins/blob/a4b4771a90484b8326fafea92fc47921492cd8a2/core/src/main/resources/jenkins/model/Jenkins/manage.jelly#L32-L55
AFAIK it cannot be used elsewhere outside this file
There was a problem hiding this comment.
@oleg-nenashev What I really wanted was to know how exercising this taglib. Some use-case.
There was a problem hiding this comment.
@recena Reusability for less repetition, see https://github.com/recena/jenkins/blob/6d119ef16946312d8c4ca319babb2e2b292b9b79/core/src/main/resources/jenkins/model/Jenkins/manage.jelly.
The October 2012 changes converted those to ManagementLinks in one loop, so it's not relevant anymore, but it was before then.
There was a problem hiding this comment.
@daniel-beck I appreciate your feedback. Can I understand we could make a cleanup?
There was a problem hiding this comment.
Assuming by cleanup you mean inlining the tag, yes.
|
|
||
| /** | ||
| * Returns true iff there are applicable but ignored (i.e. hidden) warnings. | ||
| * Returns true if there are applicable but ignored (i.e. hidden) warnings. |
There was a problem hiding this comment.
These are not typos.
iff is shorthand for if and only if, see e.g. http://www.dictionary.com/browse/iff
There was a problem hiding this comment.
My bad English. Thanks for noticing it.
|
In 8774f3c |
|
What is the benefit of these ~1500 lines of (minified) Bootstrap? |
|
@recena Any plans to continue working on it? |
|
@daniel-beck A customized version of bootstrap including some needed things. My proposal is to include Bootstrap by default in Jenkins as part of the core. @oleg-nenashev Yes, this is my plan. |
|
@recena How does this look with multiple multiple admin monitors, how does this affect the warnings popup shown on all other pages? |
|
We still need a blogpost draft to get it merged. |
|
Sure. Working on it. |
|
I think we could remove the label |
|
@jenkinsci/code-reviewers back to review |
|
@recena @daniel-beck - Is the blog post sufficient to say this has been documented? A blog post is great but is there any other actual documentation that need to change? |
|
I don't think so. My commitment was to write a blog post in order to spread the word about this improvement. |
|
@recena - Understood. 😄 I wasn't trying to shift the scope of your work. I meant to ask those driving developer documentation such as @daniel-beck @oleg-nenashev, when you say "needs-docs" are you comfortable with that being just a blog post? |
|
@bitwiseman I am fine with that, the blogpost just needs to be linked from changelog. Regarding the change, I cannot guarantee to review it this week. It depends on how serious the JEP-200 fallout is. Keeps me busy so far. Anybody else can merge it and orchestrate the delivery, but I suggest to wait till Thursday. We may need an out-of-order release tomorrow |
|
Thanks for your feedback. I hope to see these changes merged in the upcoming normal weekly. I'm planning next steps. |
|
Will I be luck on this weekly release? 😄 |
|
Sorry, I had no time to review PRs this week. I will try to review it tomorrow on the morning |
|
IMO it is ready to go. The blogpost needs the date update, but it's ready in other matters |
|
@recena would you be fine if I squash the PR during the merge? I lean towards that since there are many small changes like whitespace ones, but there is no strict policy |
|
@oleg-nenashev Sure. My personal preference is always to squash. |
|
merged |
|
Probably caused JENKINS-49129. |
| <!-- table to show a map --> | ||
| <d:tag name="feature"> | ||
| <j:set var="iconUrl" value="${icon.startsWith('/') ? resURL+icon : imagesURL+'/48x48/'+icon}"/> | ||
| ${taskTags!=null and attrs.contextMenu!='false' ? taskTags.add(href,iconUrl,title,post,requiresConfirmation) : null} |
There was a problem hiding this comment.
This line was removed without replacement.
There was a problem hiding this comment.
Indeed it looks like taskTags is involved with context menu creation, see ModelObjectWithContextMenu.java.
jenkinsci/jenkins#2857 reworked the management page, so that from core 2.103 onward, there's only one `scriptApproval` link where there had been two. So only look for 1 link in relevant core versions while still looking for two in earlier versions.

Description
See JENKINS-43786.
<table>tag usage for implementing layouts and content structures. If you need reasons or arguments.Screenshots
There are more screenshots along the PR comments.
Before
After
Changelog entries
Proposed changelog entries:
Submitter checklist
Desired reviewers
@jenkinsci/code-reviewers