spack-infrastructure icon indicating copy to clipboard operation
spack-infrastructure copied to clipboard

Published 20 hours ago • verified publisher icon spack

GitLab sometimes neglects to start a pipeline when a branch is pushed

Open zackgalbreath opened this issue 2 years ago • 2 comments

We have noticed a situation where our sync script pushes a branch to GitLab, but GitLab never starts a pipeline for it. This problem tends to confusingly manifest itself as one of the following status messages on the relevant GitHub PR:

  • pending - waiting for the style check to complete
  • pending — This branch's merge-base with develop is newer than the latest commit tested by GitLab

zackgalbreath avatar Sep 06 '22 17:09 zackgalbreath

Hey @zackgalbreath was this fixed by #317? Or are you still working on a more long term fix?

alecbcs avatar Dec 06 '22 22:12 alecbcs

Hey @zackgalbreath was this fixed by #317? Or are you still working on a more long term fix?

#317 mitigates this issue, but it doesn't fully resolve it. GitLab is still periodically failing to start pipelines for us, but now we have a cronjob to detect these skipped pipelines & start them automatically every 30 minutes.

We like to keep track of mitigated issues like this so we can keep an eye out for upstream fixes & other opportunities to properly resolve them.

zackgalbreath avatar Dec 06 '22 23:12 zackgalbreath