Parameters

Branch to test across the repositories in the .repos file that have it. For example, if you have a few repositories with the 'feature' branch, then you can set this to 'feature'. The repositories with the 'feature' branch will be changed to that branch. Other repositories will stay on the default branch, usually 'rolling'. To use the default branch on all repositories, use an empty string. This only works if the branches are on the origin; forks cannot be used. To use forks or different named branches, see CI_ROS2_REPOS_URL.

Branch of ros2/ci repository from which to get the ci scripts.

Custom .repos file to use instead of the default (https://raw.githubusercontent.com/ros2/ros2/rolling/ros2.repos). For example, copy the content of the .repos file to a GitHub Gist, modify it to your needs, and then pass the raw URL here. The repos file can contain forks, different branches on different repositories, additional repositories, etc. The repos file here should contain all of the ROS 2 repositories necessary to build; individual packages to build and test can be selected using CI_BUILD_ARGS and CI_TEST_ARGS.

Supplemental .repos file which will be merged into the default repos file. Use this instead of the Custom .repos file if you want to add to the default repos file rather than replace it.

Use a specific branch of the colcon repositories. If the branch doesn't exist fall back to the default branch. To use the latest released version, use an empty string.

Select the linux distribution to use.

Select the RHEL release to use.

Select the ROS distribution to target. Note that this only changes some of the underlying system packages installed; it does not change the default .repos file to the correct branch.

A mixin index url for colcon to use.

Select the CMake build type.

Arbitrary arguments passed to the colcon 'build' verb.

By setting this to True, the build will use the --isolated option.

By setting this to True white space will be inserted into the paths. The paths include the workspace, plus the source, build and install spaces. This tests the robustness to whitespace being within the different paths.

By setting this to True, the build will attempt to use RTI Connext DDS.

By setting this to True, the build will use the Debian packages for Connext, instead of the binaries off the RTI website (applies to Linux only).

By setting this to True, the build will attempt to use Eclipse's Cyclone DDS.

By setting this to True, the build will attempt to use eProsima's FastRTPS (static type support).

By setting this to True, the build will attempt to use eProsima's FastRTPS (dynamic type support).

By setting this to true, the build will run with clang compiler on Linux (currently ignored on non-Linux).

By setting this to true, the build will report test coverage for C/C++ code (currently ignored on non-Linux) and pytest.

Arbitrary arguments passed to the colcon 'test' verb.