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

Remove re-run from /prebuilds, redirect to logs when rerunning #8835

Merged
merged 1 commit into from
Mar 18, 2022

Conversation

laushinka
Copy link
Contributor

@laushinka laushinka commented Mar 16, 2022

Description

  1. Disallows actions in the /prebuilds page
  2. When rerunning a prebuild in the branches page, it directs to the prebuild logs view.

Related Issue(s)

Fixes #8765

How to test

https://laushinka-5100f6fadc.staging.gitpod-dev.com/projects

  1. Add a project and run prebuilds that fail.
  2. Rerun a prebuild for the failed one.

Release Notes

Rerunning prebuilds direct to the prebuild logs view, and rerunning is not allowed from the /prebuilds page.

Documentation

@laushinka laushinka changed the title try Remove re-run from /prebuilds, redirect to logs when rerunning Mar 16, 2022
@laushinka laushinka force-pushed the laushinka/dashboard-remove-action-8765 branch 2 times, most recently from c0ab888 to 3b58e1e Compare March 16, 2022 17:26
@laushinka laushinka marked this pull request as ready for review March 16, 2022 17:28
@laushinka laushinka requested review from a team, jldec and geropl March 16, 2022 17:28
@jldec
Copy link
Contributor

jldec commented Mar 16, 2022

This is good - thanks @laushinka .

The only change I would suggest (and I know this is slightly different from what was discussed in #8765) would be to remove the context dots menu from the prebuilds list entirely, and link the whole list item to the prebuild detail. If that is a running prebuild, then the Cancel action can be performed there, so we don't need it in the prebuilds list. This would improve usability and simplify the experience of navigating between the prebuilds list, and the prebuilds detail.

Copy link
Contributor

@jldec jldec left a comment

Choose a reason for hiding this comment

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

small change in navigation behavior requested in the comment

@jldec
Copy link
Contributor

jldec commented Mar 16, 2022

Redirecting from the branches list to the prebuild detail, when a prebuild is started, is a nice improvement.

@laushinka laushinka force-pushed the laushinka/dashboard-remove-action-8765 branch from 3b58e1e to bf23c34 Compare March 17, 2022 13:34
@roboquat roboquat added size/M and removed size/S labels Mar 17, 2022
@laushinka
Copy link
Contributor Author

laushinka commented Mar 17, 2022

@gtsiolis I implemented a spinner but I think I could use your review here on the positioning 🙏🏽

@laushinka
Copy link
Contributor Author

laushinka commented Mar 17, 2022

It shows build failed but that's actually an old one 🤔 The preview env is green[1]

@gtsiolis
Copy link
Contributor

gtsiolis commented Mar 17, 2022

Looking at this now! 👀

Copy link
Contributor

@gtsiolis gtsiolis left a comment

Choose a reason for hiding this comment

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

Thanks for the ping, @laushinka! 🏓

Left two comments below.

Comment on lines 373 to 379
<div>
{isLoading && (
<div className="flex justify-center">
<img alt="" className="h-4 w-4 animate-spin" src={Spinner} />
</div>
)}
</div>
Copy link
Contributor

@gtsiolis gtsiolis Mar 17, 2022

Choose a reason for hiding this comment

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

issue: This placed spinner at the bottom of the branches list can definitely could*** cause some confusion, especially if the branches list is long, etc.

*** @laushinka Sorry if the initial wording here felt a bit strong. 🙏

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're absolutely right 🙏🏽 I'll find a different position for it

Copy link
Contributor

@gtsiolis gtsiolis Mar 17, 2022

Choose a reason for hiding this comment

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

thought: If we don't have a page we can render instantly I'd avoid the redirect in the first place.

Comment on lines 373 to 379
<div>
{isLoading && (
<div className="flex justify-center">
<img alt="" className="h-4 w-4 animate-spin" src={Spinner} />
</div>
)}
</div>
Copy link
Contributor

@gtsiolis gtsiolis Mar 17, 2022

Choose a reason for hiding this comment

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

suggestion: Redirecting to the prebuild details page as @jldec described in #8835 (comment) sounds great, could we go with that approach? The prebuild details page already contains a loading indicator (spinner) at the bottom right? If for some reason the prebuild does not exist or the page is not available before some time we could introduce a new prebuild phase so that on trigger there's always a phase we can load and link to.

Let me now what you think, @laushinka! 💭

Loading indicator (spinner) on the prebuild details page
Frame 370

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes that would be ideal, unfortunately the spinner is necessary here because it takes a while until we get a response back to know which prebuild logs page to go to..

Copy link
Contributor

Choose a reason for hiding this comment

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

Alternatively, we could not attempt to redirect until we have a page we can render in time.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Alternatively, we could not attempt to redirect until we have a page we can render in time.

Hmm, how would the UX be like here? Also looping in @jldec

Copy link
Contributor

Choose a reason for hiding this comment

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

Showing a spinner near the action that the user clicked, and then redirecting after a pause, is still preferable over not redirecting at all.

@roboquat roboquat added size/L and removed size/M labels Mar 17, 2022
@laushinka laushinka force-pushed the laushinka/dashboard-remove-action-8765 branch 3 times, most recently from 6bfd371 to fdbb269 Compare March 18, 2022 13:35
@jldec
Copy link
Contributor

jldec commented Mar 18, 2022

/werft run with-vm=true

👍 started the job as gitpod-build-laushinka-dashboard-remove-action-8765.14

@laushinka laushinka force-pushed the laushinka/dashboard-remove-action-8765 branch from fdbb269 to dc4d236 Compare March 18, 2022 15:45
Copy link
Contributor

@jldec jldec left a comment

Choose a reason for hiding this comment

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

LGTM

@roboquat roboquat merged commit 6721143 into main Mar 18, 2022
@roboquat roboquat deleted the laushinka/dashboard-remove-action-8765 branch March 18, 2022 16:45
@laushinka
Copy link
Contributor Author

laushinka commented Mar 21, 2022

@gtsiolis We can improve the spinner and the general behavior of the prebuilds page in a follow-up issue 🙏🏽 cc @jldec because we talked about it briefly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[dashboard] Remove action option to re-run prebuild from prebuild list view
4 participants