Question 1

How do I integrate action-ros-ci with codecov for coverage reports?

Accepted Answer

Use the provided workflow snippet with colcon-defaults for coverage mixins and the codecov-action. You'll need a codecov.yml file to map workspace structure, as detailed in the 'Integrate with codecov' section of the README.

Question 2

Can action-ros-ci handle both ROS 1 and ROS 2 in one workflow?

Accepted Answer

Yes, you can specify both target-ros1-distro and target-ros2-distro inputs, but the action builds them sequentially in the same workspace, which may require careful dependency management to avoid conflicts.

Question 3

What's better: action-ros-ci or custom GitHub Actions for ROS?

Accepted Answer

action-ros-ci saves time by abstracting common tasks like vcs import and colcon commands with best practices, while custom actions offer more flexibility but require maintaining complex logic yourself.

Question 4

How to skip tests in action-ros-ci?

Accepted Answer

Set the skip-tests input to true, which bypasses colcon test and code coverage processing, as shown in the 'Skip tests' example in the README.

Question 5

Is action-ros-ci good for large monorepos?

Accepted Answer

It can handle large workspaces by limiting builds with the package-name input, but performance depends on dependency count and build time; using optimized container images is recommended for efficiency.

Question 6

How to use action-ros-ci with private dependencies?

Accepted Answer

Provide a personal access token via import-token, especially for private repos in vcs-repo-file-url. The README explains using secrets like REPO_TOKEN for this purpose in the 'Use with private repos' section.

action-ros-ci

What is action-ros-ci?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions