Re: How to do add-on merge requests and get a pipeline to run?

Werner LEMBERG <[email protected]> writes:

>> I added
>>
>> <https://gitlab.com/lilypond/lilypond/-/merge_requests/3115>
>>
>> which is based on
>>
>> <https://gitlab.com/lilypond/lilypond/-/merge_requests/3111>
>>
>> and the view of the commits on top of that other merge requests
>> looks ok.  However, Gitlab does not appear to start a pipeline here.
>
> I think that you have to physically add the commits from MR 3111
> before the commits of MR 3115 to make the pipeline get executed (and
> tell the users in the MR description to ignore these commits).  It
> seems that gitlab's CI doesn't support the case where you want to
> merge branch A into an arbitrary branch B.  Branch B must always be
> 'master' AFAICS.
>
> Maybe Jonas knows more.

From what I have read so far, I consider it likely that once request
3111 gets merged upstream, request 3115 will be reoriented on master and
will then presumably run the pipelines just fine.

But right now it doesn't.  Which means slow progress of projects done in
multiple steps if the first step has to go through all stages of
acceptance before the second one can even get review attention.

-- 
David Kastrup