Skip to content

Improve CI template organization

When the templates were first added GitLab-CI did not yet support nested include statements (i.e. an included yaml including other yamls recursively). This is no longer the case.

Since support for other distros is being added in a somewhat hacky way (i.e. logic depending on the branch names), it would be good to take some time to reorganize the templates to:

  • Reduce code duplication, which is almost 100% between the current rosinstall/no-rosinstall versions
  • Possibly add separate templates per target ROS distro
    • If this path is taken, it would be nice if a single branch of a given repository could choose jobs for multiple distros whenever that makes sense
  • Possibly add a configurable default job which can be reconfigured by the final user

If someone dedicates time to this (not looking at anyone, @inigo.moreno, 😉), I think it would be good to sketch/define the possible solutions before going straight ahead to implement one.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information