Read about our upcoming Code of Conduct on this issue

Commit c71226e6 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Heptapod CI: triggering heptapod-tests

Since the heptapod-tests CI now uses this image, it makes sense to
trigger it. This will give us scheduled runs, that should warn us
of client-side and test harness regressions.
parent 40c285e8bb67
Pipeline #13184 passed with stages
in 5 minutes and 41 seconds
......@@ -17,11 +17,28 @@ docker:
script:
- ./kaniko.sh
py-heptapod:
.downstreams:
rules:
- if: '$CI_COMMIT_BRANCH =~ /^branch\/.*/' # named branch (not a topic)
- when: never
stage: downstream
py-heptapod:
extends:
- .downstreams
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