Skip to content
Build Rolling Dockerfile

Use launch_utils instead of a spawner per controller #1010

Sign in to view logs

Use launch_utils instead of a spawner per controller

Use launch_utils instead of a spawner per controller #1010

Workflow file for this run

.github/workflows/rolling-docker-build.yaml at 183a6b7
name: Build Rolling Dockerfile
# description: builds the dockerfile contained within the repo
on:
pull_request:
branches:
- master
paths:
- '**.hpp'
- '**.cpp'
- Dockerfile/**
- '.github/workflows/rolling-docker-build.yml'
- '**/package.xml'
- '**/CMakeLists.txt'
- '**.xacro'
- '**.py'
- '**.yaml'
- 'ros2_control_demos.rolling.repos'
push:
branches:
- master
paths:
- '**.hpp'
- '**.cpp'
- Dockerfile/**
- '.github/workflows/rolling-docker-build.yml'
- '**/package.xml'
- '**/CMakeLists.txt'
- '**.xacro'
- '**.py'
- '**.yaml'
- 'ros2_control_demos.rolling.repos'
schedule:
# Run every morning to detect broken dependencies
- cron: '50 1 * * *'
jobs:
build:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
ROS_DISTRO: [rolling, jazzy]
steps:
- uses: actions/checkout@v4
with:
ref: master
- name: Build the Docker image
run: docker build --file Dockerfile/Dockerfile --tag ros2_control_demos_${{ matrix.ROS_DISTRO }} --build-arg ROS_DISTRO=${{ matrix.ROS_DISTRO }} .