[petsc-dev] note on submiting gitlab pipelines

Jed Brown jed at jedbrown.org
Thu Oct 31 09:52:54 CDT 2019

"Balay, Satish via petsc-dev" <petsc-dev at mcs.anl.gov> writes:

> Just a reminder:
> We've had regular changes to CI - [.gitlab-ci.yaml] - so its generally
> a good idea to rebase branches to latest maint/master before starting
> any new test pipeline.
> One can always check if .gitlab-ci.yaml was updated with:
> git fetch
> git log my-branch..master .gitlab-ci.yaml

The fetch updates 'origin/master', not 'master', so the appropriate
check is

  git log ..origin/master .gitlab-ci.yaml

When you rebase, you should try to confirm that intermediate commits on
your branch still compile (otherwise you can break bisection).

> [even without an updated .gitlab-ci.yaml - a rebase generally helps
> with better usage of package cache for the builds - thus reducing
> rebuilds of external-packages]
> Satish
> On Wed, 23 Oct 2019, Balay, Satish via petsc-dev wrote:
>> A note to all petsc developers @gitlab who start test pipelines on
>> MRs:
>> Please rebase the MR branch over latest master (or maint - if
>> appropriate) before starting the test pipeline pipeline to use latest
>> ci fixes.
>> i.e make sure e73aa2c6ed is in your branch - when the test is done.
>> Without this fix - you might see a success status even-though some
>> have tests failed. [so the results would be useless].
>> One way to check if your branch has this fix:
>> git branch --contains e73aa2c6ed <branch-name>
>> thanks,
>> Satish

More information about the petsc-dev mailing list