[petsc-dev] Pause-for-approval Pipelines?

Satish Balay balay at mcs.anl.gov
Thu Aug 27 11:45:52 CDT 2020

On Thu, 27 Aug 2020, Jacob Faibussowitsch wrote:

> 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.

The 2 pipelines you see are
- readdocs pipeline
- merge-pipeline - auto starts - does the pre stage and pauses.

> 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?

Its not a replacement for merge train.[merge train is a way to do the merge when the MR is tested and ready for merge]

However you can use this as a replacement for starting a new pipeline from the web interface https://gitlab.com/petsc/petsc/-/pipelines/new
[i.e instead of starting a web interface pipeline - you just go to the MR page - 'pipeline tab' and hit continue]

Or you can ignore this and continue to use the web interface.

> 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).

You shouldn't have to cancel the automatic MR pipeline. They should just stay paused.

And I don't remember getting e-mails from these stalled MR pipelines. Perhaps you got them because of pre-stage failures?

However if you have errors in pre stage tests - you might as well check and fix them.

The one thats causing most trouble is readdocs pipeline. Its probably best to disable it until its issues are resolved.


More information about the petsc-dev mailing list