Perceived performance on "Run pipeline" MR button is poor
Summary
When a user clicks the Run Pipeline
button a the Pipelines tab in a merge request, it takes a while before the new pipeline appears on the frontend and the user wonders whether the button has really been clicked or not due to lack of feedback. -- from Slack conversation
Steps to reproduce
Click Run pipeline
in Pipelines tab in merge request page.
What is the current bug behavior?
- Button does not provide any feedback whether the action has been submitted or not
- Either the pipeline takes long time to be created or the frontend takes long time to display it.
What is the expected correct behavior?
- User does not have to wait too long to see if they have really clicked the button or not. Feedback on the button should be immediate.
- Pipeline creation should possibly be faster and new pipeline should appear on the frontend quickly.
Propsoal
Display a toast message after Run pipeline
has been clicked to let the user know a pipeline is in the process of being created.