Repository Summary
Checkout URI | https://github.com/ros-industrial/industrial_ci.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2025-06-08 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
industrial_ci | 0.10.0 |
README
Industrial CI
CI (Continuous Integration) configuration for [ROS]{.title-ref} (Robot Operating System). This is the refactored version with ROS2 support, the old version can be found in the legacy branch. Please check the migration guide as well.
::: {.contents depth=”2”} Table of Contents :::
Detailed documentation
Other than the brief introduction in this page, you can also check the detailed doc here.
Introduction
This package contains CI (Continuous Integration) scripts that any ROS-powered packages can commonly use. Some notable feature:
- Checks if your package builds, installs without issues. If unit/system tests are defined run them. ROS Prerelease Test can optionally be run.
- Proven to cover the general requirements of the ROS-based robotics repositories. Easily configurable.
- Users can add custom pre/post processes.
- Covers ROS1 Indigo, Jade, Kinetic, Lunar, Melodic, Noetic and ROS2 distributions.
- This repo provides scripts for [Bitbucket CI]{.title-ref}, [Gitlab CI]{.title-ref}, [GitHub Actions]{.title-ref} and [Travis CI]{.title-ref} only, but it can be easily adapted for other CI services.
For a brief overall introduction, you could also check a presentation:
Quick Start
With a few steps, you can start in your client repository using CI confiurations stored in [industrial_ci]{.title-ref}.
For Travis CI
- Activate CI for your github repository on Travis CI). a) You may do so either at https://travis-ci.com/github/YOUR_GITHUB_ORGANIZATION or at https://travis-ci.com/github/YOUR_GITHUB_USER (depending on where your repository sits). b) Activate CI beta for your bitbucket repository is similar, but the target link that your status badge directs to needs to be modified from https://travis-ci.com/USERNAME/REPO_NAME to https://travis-ci.com/bitbucket/USERNAME/REPO_NAME. By default, the generated link directs to a github repository.
- Add [.travis.yml]{.title-ref} file to your repository root (complete template):
<!-- -->
language: generic
services:
- docker
env:
matrix:
- ROS_DISTRO="indigo"
install:
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .industrial_ci -b master
script:
- .industrial_ci/travis.sh
- Note: The name [.industrial_ci]{.title-ref} is NO longer REQUIRED for the cloned folder starting version 0.3.2; you can pick any name (recommended practice to keep the folder hidden (by prepending ".").
For Gitlab CI
- Enable CI for your repo. Please refer to official
doc for the steps to do
so. Note for Gitlab CI, necessary steps might be different between
hosted version (i.e. the one on gitlab.com) v.s. the one on your own
server, which Gitlab doesn't always clarify in its documentation.
- For your server version, enable a runner for your Gitlab project
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
Checkout URI | https://github.com/ros-industrial/industrial_ci.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2025-06-08 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
industrial_ci | 0.10.0 |
README
Industrial CI
CI (Continuous Integration) configuration for [ROS]{.title-ref} (Robot Operating System). This is the refactored version with ROS2 support, the old version can be found in the legacy branch. Please check the migration guide as well.
::: {.contents depth=”2”} Table of Contents :::
Detailed documentation
Other than the brief introduction in this page, you can also check the detailed doc here.
Introduction
This package contains CI (Continuous Integration) scripts that any ROS-powered packages can commonly use. Some notable feature:
- Checks if your package builds, installs without issues. If unit/system tests are defined run them. ROS Prerelease Test can optionally be run.
- Proven to cover the general requirements of the ROS-based robotics repositories. Easily configurable.
- Users can add custom pre/post processes.
- Covers ROS1 Indigo, Jade, Kinetic, Lunar, Melodic, Noetic and ROS2 distributions.
- This repo provides scripts for [Bitbucket CI]{.title-ref}, [Gitlab CI]{.title-ref}, [GitHub Actions]{.title-ref} and [Travis CI]{.title-ref} only, but it can be easily adapted for other CI services.
For a brief overall introduction, you could also check a presentation:
Quick Start
With a few steps, you can start in your client repository using CI confiurations stored in [industrial_ci]{.title-ref}.
For Travis CI
- Activate CI for your github repository on Travis CI). a) You may do so either at https://travis-ci.com/github/YOUR_GITHUB_ORGANIZATION or at https://travis-ci.com/github/YOUR_GITHUB_USER (depending on where your repository sits). b) Activate CI beta for your bitbucket repository is similar, but the target link that your status badge directs to needs to be modified from https://travis-ci.com/USERNAME/REPO_NAME to https://travis-ci.com/bitbucket/USERNAME/REPO_NAME. By default, the generated link directs to a github repository.
- Add [.travis.yml]{.title-ref} file to your repository root (complete template):
<!-- -->
language: generic
services:
- docker
env:
matrix:
- ROS_DISTRO="indigo"
install:
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .industrial_ci -b master
script:
- .industrial_ci/travis.sh
- Note: The name [.industrial_ci]{.title-ref} is NO longer REQUIRED for the cloned folder starting version 0.3.2; you can pick any name (recommended practice to keep the folder hidden (by prepending ".").
For Gitlab CI
- Enable CI for your repo. Please refer to official
doc for the steps to do
so. Note for Gitlab CI, necessary steps might be different between
hosted version (i.e. the one on gitlab.com) v.s. the one on your own
server, which Gitlab doesn't always clarify in its documentation.
- For your server version, enable a runner for your Gitlab project
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
Checkout URI | https://github.com/ros-industrial/industrial_ci.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2025-06-08 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
industrial_ci | 0.10.0 |
README
Industrial CI
CI (Continuous Integration) configuration for [ROS]{.title-ref} (Robot Operating System). This is the refactored version with ROS2 support, the old version can be found in the legacy branch. Please check the migration guide as well.
::: {.contents depth=”2”} Table of Contents :::
Detailed documentation
Other than the brief introduction in this page, you can also check the detailed doc here.
Introduction
This package contains CI (Continuous Integration) scripts that any ROS-powered packages can commonly use. Some notable feature:
- Checks if your package builds, installs without issues. If unit/system tests are defined run them. ROS Prerelease Test can optionally be run.
- Proven to cover the general requirements of the ROS-based robotics repositories. Easily configurable.
- Users can add custom pre/post processes.
- Covers ROS1 Indigo, Jade, Kinetic, Lunar, Melodic, Noetic and ROS2 distributions.
- This repo provides scripts for [Bitbucket CI]{.title-ref}, [Gitlab CI]{.title-ref}, [GitHub Actions]{.title-ref} and [Travis CI]{.title-ref} only, but it can be easily adapted for other CI services.
For a brief overall introduction, you could also check a presentation:
Quick Start
With a few steps, you can start in your client repository using CI confiurations stored in [industrial_ci]{.title-ref}.
For Travis CI
- Activate CI for your github repository on Travis CI). a) You may do so either at https://travis-ci.com/github/YOUR_GITHUB_ORGANIZATION or at https://travis-ci.com/github/YOUR_GITHUB_USER (depending on where your repository sits). b) Activate CI beta for your bitbucket repository is similar, but the target link that your status badge directs to needs to be modified from https://travis-ci.com/USERNAME/REPO_NAME to https://travis-ci.com/bitbucket/USERNAME/REPO_NAME. By default, the generated link directs to a github repository.
- Add [.travis.yml]{.title-ref} file to your repository root (complete template):
<!-- -->
language: generic
services:
- docker
env:
matrix:
- ROS_DISTRO="indigo"
install:
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .industrial_ci -b master
script:
- .industrial_ci/travis.sh
- Note: The name [.industrial_ci]{.title-ref} is NO longer REQUIRED for the cloned folder starting version 0.3.2; you can pick any name (recommended practice to keep the folder hidden (by prepending ".").
For Gitlab CI
- Enable CI for your repo. Please refer to official
doc for the steps to do
so. Note for Gitlab CI, necessary steps might be different between
hosted version (i.e. the one on gitlab.com) v.s. the one on your own
server, which Gitlab doesn't always clarify in its documentation.
- For your server version, enable a runner for your Gitlab project
File truncated at 100 lines see the full file