Commit 5d9d3b21 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Stop triggering heptapod-tests

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)
parent a3bf97e5c3b3
Pipeline #16948 passed with stages
in 6 minutes and 35 seconds
......@@ -29,16 +29,3 @@
trigger:
project: heptapod/py-heptapod
branch: branch/$CI_COMMIT_HG_BRANCH
heptapod-functional-tests:
extends:
- .downstreams
trigger:
project: heptapod/heptapod-tests
# In truth, since the impact on Heptapod functional tests of changes in this
# base image are on the client side or in test harness, the branch to trigger
# has no deep logical connection with the branch of this image, hence the
# current Heptapod series. But it's interesting to trigger both branches
# of heptapod-tests (just once). Tying them to the branch of this image is a
# simple way to achieve that.
branch: branch/$CI_COMMIT_HG_BRANCH
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment