GitLab has been upgraded to 13.7.4 If you encounter any issues mail

Commit 6a7e6b2b authored by Ben Avison's avatar Ben Avison

Fix pipeline failures for established forks

If the following happens:
* a GitLab runner recursively clones a superproject
* one or more submodules has changes upstream and the submodule references in
  the superproject have been updated to point to it
* a new pipeline is launched for the new superproject revision

then, while the runner would fetch changes to the superproject, it wasn't
doing so for the submodules. Ironically, we do both `git submodule update`
and `git submodule update --remote` in different pipeline stages and the
latter includes an implicit submodule fetch - but that was the later stage
which we don't get as far as.

To fix this, while retaining the pipeline stage order, include an explicit
fetch in the earlier stage (and remove the implicit fetch in the later one,
since that now merely wastes time).
parent 9c61e2f0
Pipeline #708 failed with stage
in 2 seconds