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

[JENKINS-72020] Restore ability to reorder clouds #8492

Merged
merged 11 commits into from
Oct 11, 2023

Conversation

Vlatombe
Copy link
Member

@Vlatombe Vlatombe commented Sep 15, 2023

Adding back controls to reorder clouds.

Since clouds order is taken into account for node provisioning, users should be able to reorder them as needed.

Enregistrement.de.l.ecran.2023-10-09.a.18.06.15.mov

See JENKINS-72020.

Testing done

Proposed changelog entries

  • Allow clouds to be reordered. This was previously possible, but disappeared when the cloud management was moved to a separate page (regression in 2.403).

Proposed upgrade guidelines

N/A

Submitter checklist

Desired reviewers

@mention

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

Maintainer checklist

Adding back controls to reorder clouds.

Since clouds order is taken into account for node provisioning, users should be able to reorder them as needed.
@Vlatombe Vlatombe added the regression-fix Pull request that fixes a regression in one of the previous Jenkins releases label Sep 15, 2023
@Vlatombe Vlatombe marked this pull request as ready for review September 15, 2023 15:38
<a href="move" class="jenkins-table__button">
<input type="hidden" name="name" value="${cloud.name}"/>
<j:if test="${not status.first}">
<f:submit name="up" value="" icon="symbol-chevron-up"/>
Copy link
Member

Choose a reason for hiding this comment

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

I think a tertiary or button with a symbol would look less intrusive, especially if you have multiple clouds set up: https://weekly.ci.jenkins.io/design-library/Buttons/

Copy link
Member Author

Choose a reason for hiding this comment

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

I updated the PR with tertiary buttons. Let me know what you think!

Copy link
Member

Choose a reason for hiding this comment

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

Thanks!

@Vlatombe Vlatombe requested a review from NotMyFault September 18, 2023 08:00
@Vlatombe Vlatombe requested a review from a team September 18, 2023 16:31
timja

This comment was marked as outdated.

@Vlatombe

This comment was marked as outdated.

@NotMyFault NotMyFault self-requested a review September 20, 2023 14:03
@Vlatombe Vlatombe requested a review from timja September 20, 2023 15:06
@timja
Copy link
Member

timja commented Sep 20, 2023

(Still not a huge fan of the UX, I've pulled it locally and when I get a chance in the next day or two hopefully I can propose something better)

@Vlatombe
Copy link
Member Author

Thanks @timja ! Let me know if you find something better.

@timja

This comment was marked as outdated.

@timja timja added web-ui The PR includes WebUI changes which may need special expertise needs-comments-resolved Comments in the PR need to be addressed before it can be considered for merging labels Sep 24, 2023
@Vlatombe
Copy link
Member Author

Getting further, I included your first option and a save button. Still not fully satisfied with the save usability though.

@timja
Copy link
Member

timja commented Sep 25, 2023

Getting further, I included your first option and a save button. Still not fully satisfied with the save usability though.

you could probably call submit the form async in some way in the on complete, or have the save button made visible after re-arranging?

Not the best as it seems a bit weird to have a save button on this page

Only display order column when admin
@Vlatombe Vlatombe requested a review from timja September 25, 2023 13:57
<thead>
<tr>
<l:isAdmin>
<th class="jenkins-table__cell--tight">Order</th>
Copy link
Member

@timja timja Sep 25, 2023

Choose a reason for hiding this comment

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

Looking at the video this seems a bit mis-aligned, we could possibly drop the label in favour of a tooltip on the handle?

Copy link
Member Author

Choose a reason for hiding this comment

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

Should be slightly better now.

@Vlatombe Vlatombe requested a review from timja September 26, 2023 08:08
@Vlatombe
Copy link
Member Author

What do you think about this?

I prefer the version where the handle is on the left.

The other option might be to just drop the cloud icon as well?

I think once cloud implementations catch up with providing proper icons this will improve the page usability.

Also considered making the icon the drag & drop handle (like you would in a file explorer) but doesn't seem trivial with current dd component.

@timja
Copy link
Member

timja commented Sep 27, 2023

I think once cloud implementations catch up with providing proper icons this will improve the page usability.

It's not really about catching up it's licensing, at least with Azure it's damn hard to get the license -.-.
Neither myself or people in Microsoft managed to get anywhere for the Azure plugins...

@timja
Copy link
Member

timja commented Sep 27, 2023

I also prefer it on the left, but double icons doesn't feel right to me
cc @janfaracik if you have any input

@Vlatombe
Copy link
Member Author

Vlatombe commented Oct 2, 2023

I merged the two columns, the cloud icon can now be used as a drag-and-drop handle.

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.

Works for me

@NotMyFault NotMyFault removed the needs-comments-resolved Comments in the PR need to be addressed before it can be considered for merging label Oct 3, 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.

🚀

@timja
Copy link
Member

timja commented Oct 3, 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 Oct 3, 2023
@MarkEWaite
Copy link
Contributor

@Wadeck would the security team like to review this before merge?

@Wadeck
Copy link
Contributor

Wadeck commented Oct 5, 2023

@MarkEWaite Yes please, I think we have forgotten to add a comment / label at this point :(

@Wadeck Wadeck added the needs-security-review Awaiting review by a security team member label Oct 5, 2023
@MarkEWaite MarkEWaite removed the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Oct 5, 2023
Copy link
Member

@daniel-beck daniel-beck left a comment

Choose a reason for hiding this comment

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

Requesting change for the vulnerability.

As a general note, it's not obvious why cloud order matters (and in the current iteration, how to change it, as noted in a line comment). Ideally above or below the clouds list, the impact of order on behavior should be explained.

Comment on lines +61 to +63
<div class="jenkins-table__cell__button-wrapper dd-handle">
<l:icon src="${cloud.iconClassName}" tooltip="${cloud.iconAltText}"/>
</div>
Copy link
Member

Choose a reason for hiding this comment

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

IMO: This was nicer as in the video, it's too difficult to discover currently.

@Vlatombe Vlatombe requested a review from daniel-beck October 9, 2023 16:05
@daniel-beck daniel-beck dismissed their stale review October 9, 2023 18:17

security issue was addressed

@daniel-beck daniel-beck added security-approved @jenkinsci/core-security-review reviewed this PR for security issues and removed needs-security-review Awaiting review by a security team member labels Oct 9, 2023
@timja
Copy link
Member

timja commented Oct 10, 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 Oct 10, 2023
@NotMyFault NotMyFault merged commit 16bca2e into jenkinsci:master Oct 11, 2023
16 checks passed
@Vlatombe Vlatombe deleted the reorder-clouds-JENKINS-72020 branch October 12, 2023 07:20
@timja
Copy link
Member

timja commented Oct 12, 2023

IMO: This was nicer as in the video, it's too difficult to discover currently.

This was discussed at the UX sig yesterday, https://docs.google.com/document/d/1QttPwdimNP_120JukigKsRuBvMr34KZhVfsbgq1HFLM/edit?pli=1

Christina is going to try come up with a design for a next iteration.
We agreed the issue is non blocking.

@MarkEWaite
Copy link
Contributor

Should this be backported into the 2.426.1 LTS release?

@timja
Copy link
Member

timja commented Oct 29, 2023

Yes makes sense

MarkEWaite pushed a commit to MarkEWaite/jenkins that referenced this pull request Oct 29, 2023
* [JENKINS-72020] Reorder clouds

Adding back controls to reorder clouds.

Since clouds order is taken into account for node provisioning, users should be able to reorder them as needed.

* Use tertiary buttons

* Separate screen for reordering

* Include reordering in the cloud list directly (thanks @timja)

* Show the save button after the first reordering

* Separate JS

Only display order column when admin

* Fix reviews

* Remove unused string

* Put drag-and-drop handle in the cloud icon column

* Add missing permission check

* Add a small blurb to clarify what cloud order is used for.

(cherry picked from commit 16bca2e)
@MarkEWaite MarkEWaite mentioned this pull request Oct 29, 2023
14 tasks
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 regression-fix Pull request that fixes a regression in one of the previous Jenkins releases 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
Development

Successfully merging this pull request may close these issues.

6 participants