Skip to content

CI: Pin ros2-rolling to Ubuntu Noble until Rolling ships for Resolute (26.04)#1157

Open
wooksong wants to merge 1 commit into
BehaviorTree:masterfrom
wooksong:ci/fix-ros2-rolling-noble
Open

CI: Pin ros2-rolling to Ubuntu Noble until Rolling ships for Resolute (26.04)#1157
wooksong wants to merge 1 commit into
BehaviorTree:masterfrom
wooksong:ci/fix-ros2-rolling-noble

Conversation

@wooksong

@wooksong wooksong commented Jul 1, 2026

Copy link
Copy Markdown

Problem

industrial_ci@master now resolves ROS_DISTRO=rolling to ubuntu:resolute (Ubuntu 26.04) — Rolling's new target platform. But Rolling debs aren't published for resolute yet, so setup_rosdep fails on every PR:

$ docker pull ubuntu:resolute
...
$ sudo apt-get -qq install -y --no-upgrade --no-install-recommends ros-rolling-ros-environment
E: Unable to locate package ros-rolling-ros-environment
'setup_rosdep' returned with code '100'

Confirmed directly against the ROS 2 apt repo (packages.ros.org/ros2/ubuntu):

Codename ros-rolling-ros-environment
resolute (26.04, new default) missing
noble (24.04) present

This is deterministic (not flaky) and hits all open PRs; it will stay red until the ROS build farm rebuilds Rolling for 26.04.

Fix

Pin the rolling job to Ubuntu Noble with OS_CODE_NAME: noble. industrial_ci explicitly supports rolling-on-noble (industrial_ci/src/ros.sh) and auto-pins the distro index to the last Noble-compatible snapshot (rolling/2026-04-28), so the check keeps actually building rather than being red or ignored.

- {ROS_DISTRO: rolling, ROS_REPO: main, OS_CODE_NAME: noble}

industrial_ci maps ROS_DISTRO=rolling to ubuntu:resolute (26.04), but
rolling debs are not published for resolute yet, so setup_rosdep fails
with "Unable to locate package ros-rolling-ros-environment". Pin the job
to noble (24.04), which industrial_ci supports for rolling. Revert once
rolling is published for resolute.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant