Make CI/CD job 'retry' available for MR's target project users

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

Many times, when working with community contributors on some Merge Requests, I was hitting an issue where a failing job was a blocker. To make it more descriptive:

  1. contributor opens a MR (from source project - most probably under hist personal namespace, to target project where I have developer/master access),
  2. we're working together on making the MR possible to be merged (contributor, me and possibly others are commenting the changes and discussing about the MR; contributor is pushing updates to the branch),
  3. the work is done, I'm approving changes and clicking Merge when pipeline succeeds,
  4. the pipeline fails because of random job failure not because of the added changes,
  5. I'm asking a contributor to retry a failing job,
  6. contributor is unavailable (he's out, he's computer exploded, he abandoned the MR or any other reason)
  7. eventually , he MR can't be merged because of a randomly failing job

The problem here is that the whole work is blocked by one randomly failing job which can be retried only by an external contributor. In such situation I could just retry this job to make pipeline passing and finally merge the MR.

Currently this is impossible if I - the maintainer of target project - am not a member of the source project.

Proposal

Make retry button in a CI/CD job available for target project users (developers and masters), when the pipeline is connected to a MR.

Edited by 🤖 GitLab Bot 🤖