Merge request pipelines for forks for post-merge result

Problem to solve

Today, fork merge requests do not create merge requests pipelines for the merged ref:

Intended users

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

• For GitHub mirroring specifically, discussed in https://gitlab.com/gitlab-org/gitlab-ee/issues/5667
• A possible alternative would be to have a pulling mechanism, such that the forked project creates the merged ref inside of that fork and runs it there: https://gitlab.com/gitlab-org/gitlab-ce/issues/55013.

Interested customers

• https://gitlab.my.salesforce.com/0016100001NkpKR
• https://gitlab.my.salesforce.com/0016100001ZzcXy

changed the description

marked this issue as related to #11934 (closed)

changed milestone to %Backlog

added Category:Continuous Integration UX devopsverify typefeature + 1 deleted label

marked this issue as related to #7380 (closed)

changed milestone to %11.10

added Category:Continuous Delivery Deliverable DogfoodingRebuild in GitLab GitLab Premium PM Ready Product Vision 2018 backend customer devopsrelease [DEPRECATED] direction documentation frontend internal customer missed-deliverable missed:11.9 + 1 deleted label and removed devopsverify label

Copied metadata from the original issue. Removing the irrelevant information

changed milestone to %Backlog

removed Deliverable PM Ready missed-deliverable + 1 deleted label

removed DogfoodingRebuild in GitLab internal customer missed:11.9 labels

changed the description

changed the description

mentioned in issue #9713 (closed)

I don't fully understand the relationship between this issue and https://gitlab.com/gitlab-org/gitlab-ee/issues/11934. Is this issue a potential follow up to that one? Or are they independent? Part of it is the message there is confusing (https://gitlab.com/gitlab-org/gitlab-ce/issues/62137 has some improvements for messaging.) @dosuken123 can you help us understand the difference between these two?

added [deprecated] Accepting merge requests label

A Premium customer with 7500 users is interested in this... https://gitlab.my.salesforce.com/00161000004yLEy

Setting ~"group::progressive delivery" based on ~"continuous delivery".

added grouprelease [DEPRECATED] label

Added milestone 12.7

changed milestone to %12.7

@jlenny this is tagged with vision 2018 - should this be upgraded to vision FY20 or simply removed as it was not tended for

Ya, this was part of the calendar year Product Vision 2018. That label isn't really used anymore so we can update to Product Vision FY20

added Product Vision FY20 label

added Enterprise Edition label

removed Category:Continuous Integration label

For what it's worth we in the Haskell installation (#55039) are blocked on this before we can move away from Marge bot for merging and instead adopt Merge Trains.

Is this duplicate of #11934 (closed)?

removed Product Vision 2018 label

Moving to 12.8 - we should check if #11934 (closed) solves this- it is currently being worked on in 12,6 . If it does't solve the problem we will revisit this issue

changed milestone to %12.8

Moving to 13.0 as #11934 (closed) is not released yet

changed milestone to %13.0

changed milestone to %12.9

changed milestone to %12.10

added needs weight label

@dosuken123 should this move to Category:Merge Trains ?

moving to the backlog for now

changed milestone to %Backlog

@ogolowinski This is a duplicate of #11934 (closed).

marked this issue as a duplicate of #11934 (closed)

closed