mikaelarguedas / ros2ci

CI integration scripts for ROS2 repositories

ros2ci

CI integration scripts for ROS2 repositories

This repository provides scripts to easily run CI for repository containing ROS 2 packages. These scripts are experimental and subject to change.

ROS 2 distributions supported:

• Crystal
• Dashing
• Eloquent
• nightly builds

Operating Systems supported

• Ubuntu Bionic (18.04)

Supported CI systems

• travisCI

How to set it up

• example of .travis.yml file

ros2ci's Issues

Github Actions / CI

Github actions with CI support is now live and could be a good platform for multi-platform CI: https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/

appveyor support

support appveyor (+ Docker in appveyor?)
cache nightly ros2 archives
build + test subset of packages on top

resource to check out https://stefanscherer.github.io/setup-windows-docker-ci-appveyor/

Any official support plan for ros2ci from OSRF?

Hi,

As the title says, do OSRF have any plans for official ros2ci support?
I can see a repository for docker images but nothing for ros2ci.

Thanks!
Ryan

Template dockerfiles

Currently the nightly and crystal dockerfiles are identical except from the base image. They should be templated to not duplicate most of the files.

Additional consideration: consider templating the dependency list but it is not changing much so it may not be necessary

Ament_python not found

I've been learning some ROS2 lately and (as the good boy my parent raised me) wanted to setup CI for it so started using this repo.

However, I get this error:

ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
telegram_ros2: Cannot locate rosdep definition for [ament_python]

(See https://travis-ci.org/github/LoyVanBeek/telegram_ros2/jobs/663494148#L1100)

Now I'm confused: ament_python is the buildtool_depend since this is a Python pkg and started with ros2 pkg create --build-type ament_python <package_name> in accordance with https://index.ros.org/doc/ros2/Tutorials/Creating-Your-First-ROS2-Package/.

But ament_python never mentioned in https://github.com/ros/rosdistro/blob/93d6478cf9ec083780c03cc58821915a3b057cf9/eloquent/distribution.yaml#L9 and the repo is empty too.

So what is off here? I'm not even sure this is the right place to ask, sorry if not.

Remove workaround setting ROS_PACKAGE_PATH

Remove

ros2ci/Dockerfile

Line 48 in baa9ca1

ENV ROS_PACKAGE_PATH=$ROS2_UNDERLAY_WS/install/share:$ROS_PACKAGE_PATH

Requires rosdep detecting ROS 2 packages: ros-infrastructure/rosdep#660

Build additional repos in underlay workspace

currently "additional repos" are built along the repo using the CI.
They should be in an underlay workspace, built first, not tested and then sourced before building and testing the overlay

Job type to detect dependency issues

currently the crystal job is based on ros-base and sources all of ros_base before building. This means that if the repo needs some packages included in ros_base without declaring a dependency on them it would not be detected by CI.

Additional considerations:
It is a tradeoff as jobs would take longer and repositories with multiple packages will likely face the issues regardless as if one package declares a dependency it will be installed for the entire workspace, shadowing missing dependencies in other packages

consider Azure pipelines

https://azure.microsoft.com/en-us/services/devops/pipelines/

Implement docker image caching

This will save setup time for each job

macos support

Travis (not likely)? CircleCI ? something else? research needed