-
Georges Racinet authored
While it's fine for scheduled pipelines, as it gives us nightlies for heptapod-tests too, it is a pain a causes enery waste or resource exhaustion while working on the CI image itself. We should schedule heptapod-tests independently, and it could eventually not use this image (there's not much reason to, apart from tox and fairly recent Mercurial and hg-evolve)
5d9d3b21eb7a
Validating GitLab CI configuration…
Learn more