Merge Train failed job without reason
Summary
When an MR is added to a merge train it may be removed but the reasons are not well explained. This can be even more confusing for users when they see their username removed the MR but they did not, when it can be re-added after an "un-mergable) and succeeds, when it fails silently and other behavior.
Summary
Normally, when a job fails, you can rerun it from the popover or by clicking into the job. The same isn't true for an MR run from a Merge Train -- for those, you have to navigate to the Pipelines page. However, there is no affordance to indicate that's the right action to take.
Steps to reproduce
- Create an MR you know will have a job fail
- Add to the Merge Train
Example Project
What is the current bug behavior?
- The pipeline needs to be rerun
What is the expected correct behavior?
Allow re-running jobs from the mini-graph for pipelines that run for merge trains.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)