make gh actions on pair with ros2_controllers

[Karsten1987]

connected to ros-controls/ros2_controllers#98

[destogl]

I would to have three jobs:

1. industrial_ci with main
2. industrial_ci with testing
3. ros_tooling for source build

[Karsten1987]

industrial_ci with main

What would be the difference between main and testing? I would assume that main would regularly fail due to synchronization delays.

[bmagyar]

Let's do 1-2 and discuss 3 when we are done with the foxy release?

[Karsten1987]

can I merge then?

[destogl]

industrial_ci with main

What would be the difference between main and testing? I would assume that main would regularly fail due to synchronization delays.

Main give a test against released packages. Usually useful when developing only on one package.
Testing shows you the status in advance.

This is not only important for PRs, but also daily builds to see upcoming errors....

[Karsten1987]

Main give a test against released packages. Usually useful when developing only on one package.
Testing shows you the status in advance.

Not sure I understand this. The way I see this is that "testing" is using the ROS2 testing apt-repo, whereas main refers to the synced one. That being said, I don't see a point to test towards "main", as this is not anything we control, but rather whenever the ROS boss triggers a sync from testing to main.

[bmagyar]

I can tell from experience that it's important to test against both.

Ideally you'd want to compile all green against main, but sometimes you may be out of sync and require stuff from testing for everything to work. There's a typical 2-week delay between the two which can be bridged by having both in the CI.

If the failure happens the other way, it means that someone broke something they probably shouldn't have, you can either adapt to fix (typically happens with dependency chains) or flag it up (API mishap).

[Karsten1987]

@destogl @bmagyar please review.

[destogl]

@bmagyar If the ros-tooling makes problems in the future, we can also use industrial_ci for source builds.