Hello All,

Why does one pipeline request spawn two separate pipelines now? Specifically 
one is a normal pipeline whereas the other includes some sort of manual 
approval button which “runs” indefinitely if you don’t either cancel it or 
approve it. I think this was somewhat discussed in a previous MR 
(https://gitlab.com/petsc/petsc/-/merge_requests/3063 
<https://gitlab.com/petsc/petsc/-/merge_requests/3063>) which indicates it is 
useful for doing a pipeline of the branch+destination but how is this different 
from the existing merge-train infrastructure that was already in place? It is 
annoying to have to manually go in and cancel the phony pipeline every time 
(not to mention twice as many emails from gitlab notifying me the femtosecond 
these pipelines fail).

Best regards,

Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391

Reply via email to