Binary builds and functional tests for upstream merges
Because we're more and more relying on tools to automate the process of merging GitLab upstream changes into Heptapod, we need a mechanism to validate the resulting Merge Requests more fully, with a Docker image build and functional tests.
Steps
-
trigger the tarball job of Heptapod Rails for MRs with the Upstream merge
label -
in the tarball job, provide the resulting version as artifacts -
trigger a downstream Omnibus pipeline, passing down the versions artifacts -
in Omnibus, read versions from the artifacts -
make the Omnibus pipeline depend on the results of its downstream Heptapod Tests pipeline
We need the artifacts because the versions information is more complicated that just the content of CI/CD variables.