Skip to content

WIP: Pick the right release for the Docker env for the target branch

The current job deinition assumes only v2019pre.

However, we need to support multiple releases at the same time.

In particular, in 2019Q3 we need to target:

  • v2019pre if urgent fixes are needed by those who switched already
  • v2019 as the upcoming stable release
  • v2020dev0 as the first step leading to the v2020 release

The pipeline definition now does the following:

  • branches starting with apertis/ will pick the matching docker image, building commits that get landed to the main branches
  • merge request targeting branches starting with apertis/ will pick the matching docker image, building commits submitted for inclusion into the main branches
  • everthing else is ignored

This is totally untested

Merge request reports