Why does a MR get 2 pipelines?

James Browning jamesb192 at jamesb192.com
Tue May 26 19:04:48 UTC 2026


> On 05/26/2026 10:54 AM PDT Hal Murray via devel <devel at ntpsec.org> wrote:
> 
>  
> https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1502
> 
> It has one at the top, and another 3 boxes down.
> 
> Merge train pipeline #2554128806 passed
> Pipeline #2554134164 running

It generates a CI pipeline on push and another on merge request. So, since  flubbed the first try...

https://gitlab.com/jamesb_fe80/ntpsec/-/pipelines/2553818135
https://gitlab.com/jamesb_fe80/ntpsec/-/pipelines/2553835433
https://gitlab.com/jamesb_fe80/ntpsec/-/pipelines/2553848302
https://gitlab.com/jamesb_fe80/ntpsec/-/pipelines/2553848456

and at NTPsec/ntpsec one to test the merge and one once it's done.

https://gitlab.com/NTPsec/ntpsec/-/pipelines/2554128806
https://gitlab.com/NTPsec/ntpsec/-/pipelines/2554134164

I dunno, it works or it doesn't; I don't always understand why.


More information about the devel mailing list