Resolve "Improve CI template organization"
Closes #35 (closed)
Edited by Iñigo Moreno i Caireta
Merge request reports
Activity
assigned to @inigo.moreno
added 1 commit
- 6f776a62 - With rosinstall now just includes no rosinstall
@jon.azpiazu @miguel.prada I have a small working version of my proposed changes:
-
.gitlab-industrial-ci-no-rosinstall.yml
now has most of the gitlab logic -
.gitlab-industrial-ci-with-rosinstall.yml
just includes the no-rosinstall version and changes the template -
.gitlab-industrial-ci-kinetic-*-rosinstall.yml
include their respective main yml and set a variableDEFAULT_DISTRO
tokinetic
- It has a workflow that checks the commit branch name and overwrites the variable
DEFAULT_DISTRO
accordingly. - Each distro is built if it matches with the
DEFAULT_DISTRO
or if a variableBUILD_KINETIC
is set.
Using this approach:
- The behaviour of
gitlab-industrial-ci-kinetic-*-rosinstall.yml
remains unchanged, as it builds the distro depending on the branch name and defaults to kinetic (see pipelines #55811 #55812 #55813 #55813 #55814 ¹ ). - We could easily create
gitlab-industrial-ci-melodic-with-rosinstall.yml
- One can set up the CI to test compile multiple distros of ROS by including
.gitlab-industrial-ci-no-rosinstall.yml
and setting theBUILD_KINETIC
andBUILD_MELODIC
variables. (See this ci definition and its pipeline #55816 ¹ )
Notes:
- These pipelines run on branches that were made from the main of dummy_application, which works on kinetic and melodic, but not on noetic.
-
- Resolved by Iñigo Moreno i Caireta
- Resolved by Iñigo Moreno i Caireta
Please register or sign in to reply