@Pyo Please post any follow up conversation to a different place since this category is only intended for announcements etc. and reaches too many people. Either to the Next Generation ROS category or answers.ros.org.
I guess the right statement would be: industrial_ci doesn’t support ROS 2 (rather than the other way around).
The official ROS buildfarm has the same capabilities for ROS 2 as for ROS 1. When releasing your repositories you should make sure to:
- add a
sourceentry torosdistro. Based on that adeveljob will be created which will build new commits on the target branch shortly after they are pushed (and in case of problems send notification emails to the maintainers listed in the packages). - choose to enable pull request testing. Based on that a
prjob will be created which will build commits on PRs targeting the specific branch and report back with the status through the GitHub UI.
If you don’t want to leverage the official ROS buildfarm you can still use the logic provided by the package which powers it by using the scripts locally or withing a CI provider like Travis: see the docs for more information about that.
I am not aware which of the other CI approaches support ROS 2 atm.
Cheers,
- Dirk