To clarify: CI uses .gitlab-ci.yaml from the branch - and not the latest from maint/master - so if your branch has old version of this file, and start a pipeline on it - it will get stuck - and timeout.
To determine if your branch has this .gitlab-ci.yaml change [requiring a rebase] - see if it has the commit: git branch --contains 0b416d8e105a765da5769e4b7feab5986dc829a2 Satish On Wed, 29 Jan 2020, Balay, Satish via petsc-dev wrote: > PETSc devs using CI@gitlab, > > With the current CI changes - before starting a test pipeline on a > branch at gitlab, its best to rebase the branch over current master as > of now [or maint - if appropriate]. > > If a test pipeline is created with non-rebased branch, some of the > stage-2 jobs will be stuck - so the pipeline won't complete. > > Satish >
