Commit d71622f9 authored by Pierre-Yves David's avatar Pierre-Yves David 🐙
Browse files

heptapod-ci: automatically refresh existing phabricator Diff on push

If a changeset have been submitted to Phabricator and a new version is pushed to
heptapod, we should refresh the state on Phabricator. If we do not do this, they
are a risk of an older version being applied from Phabricator. In this situation
content-divergence will be (rightfully) detected by evolution.

We only refresh the Diff if the test pass, to avoid updating Phabricator with
broken content.

Differential Revision: https://phab.mercurial-scm.org/D9451
parent 84e9df3186ca
Pipeline #13593 passed with stages
in 2 minutes and 58 seconds
stages: stages:
- tests - tests
- phabricator
image: registry.heptapod.net/mercurial/ci-images/mercurial-core image: registry.heptapod.net/mercurial/ci-images/mercurial-core
...@@ -39,3 +40,8 @@ ...@@ -39,3 +40,8 @@
<<: *rust_cargo_test <<: *rust_cargo_test
variables: variables:
PYTHON: python3 PYTHON: python3
phabricator-refresh:
stage: phabricator
script:
- ./contrib/phab-refresh-stack.sh
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