These pipelines will try to detect the ROS distro from the branch name. For example, if the branch starts with noetic- it will build for noetic. If the branch doesn’t start with any ROS distro, it will build the default distro, which can be specified with the variable DEFAULT_DISTRO. For convenience and backwards compatibility, some templates are provided that already set this variable:

• .gitlab-industrial-ci-kinetic-no-rosinstall.yml

• .gitlab-industrial-ci-melodic-no-rosinstall.yml

• .gitlab-industrial-ci-noetic-no-rosinstall.yml

• And the same with the with-rosinstall files.

If a repo wants to compile using multiple distributions, one can specify them by setting the BUILD variables:

All files follow the same pipeline, consisting of the following stages and jobs:

• Stage: build

  • Check python syntax

  • Run industrial_ci

    • Uses the ros distro defined above

    • Uses flexbotics-base-devel as a starting image

    • Runs scripts/ci_run_entry_points.sh in the BEFORE_SCRIPT stage, which in turn finds and runs every ci_entry_script.bash script found in the source tree (target repo + repos from .rosinstall)

  • Only when tags are pushed:

    • Run some cleanup in the industrial_ci context (e.g. delete sources)

    • Commit image used by industrial_ci

    • Build deployment image on top of it and push it to our registry

• Stage: .post (jobs in this stage are allowed to fail)

  • Check bash/sh script syntax

  • Check Markdown syntax

  • Check files have no trailing whitespace and are UTF-8 encoded

It is important to note that both images set the variable GIT_LFS_SKIP_SMUDGE, which means that when the repositories are cloned/fetched, the files hosted using Git LFS will not be downloaded. An example on how to explicitely fetch the files from LFS can be found in the common_config repository.