Merge upstream Omnibus GitLab into Omnibus Heptapod
Brings in 54 non-merge commits and goes up to the v17.0.0rc42 branching point.
Merge request reports
Activity
added Upstream merge label
enabled an automatic merge when the pipeline for 609291e313ea succeeds
The CI/CD setup for Omnibus is clearly not ready yet for this new use-case, the build fails because the value of
HEPTAPOD_VERSION
isheptapod.17.0.0.pre
, for which there is of course no tarball (worse, it is interpreted as a tagged version, hence the source downloads is not from theintermediate
subdir).Nevertheless, we are still experimenting with automated upstream merge, and would have previously not launched the full packaging.
Moreover, I launched a manual pipeline with the variable to use the tarball from heptapod!752 (closed). I then had to launch the [heptapod-tests pipeline)(https://foss.heptapod.net/heptapod/heptapod-tests/-/pipelines/81792) also manually (probably I mispelled the wished name in the Omnibus pipeline variables) and… it worked! Since I carefully checked that the image the latter ran on was really on heptapod@52846732b748, we are good to go.
Edited by Georges Racinetmentioned in merge request heptapod!752 (closed)