Does ROS 2 provide an automatic rollback command after a failed package upgrade?

Question

GoalDetermine whether ROS 2 includes a built‑in command that can automatically revert a workspace to the previously installed package versions after a failed upgrade, without requiring manual version‑control steps.Constraints arise because ROS 2 upgrades are performed with colcon build (or catkin_make for ROS 1) and dependencies are updated via rosdep. Overlay workspaces let developers test new versions alongside the installed ones, but they do not provide an automatic rollback path when the build fails, and there is no documented ROS‑wide mechanism that records prior package versions for bulk restoration.Uncertainty remains about whether the rosdistro metadata or release repositories could be leveraged to create such a rollback tool, or if developers must rely on external practices like committing source changes and rebuilding from a known good commit.Does ROS 2 currently provide a command that automatically rolls back all upgraded packages to their former versions after a failed colcon build?If no such command exists, what are the recommended, version‑control‑free strategies for achieving a safe workspace rollback?

Tasadduq Burney · Answer

AnswerNo, ROS 2 does not provide a built‑in command that automatically reverts a workspace to the previously installed package versions after a failed colcon build.Confirmed factsThe colcon --help output shows no rollback‑related subcommand.Source inspection of the colcon repository (github.com/ros2/colcon) finds no implementation that records or restores prior package versions.ROS 2 documentation does not mention any automatic rollback mechanism for package upgrades.Likely explanationROS 2 upgrade tools (colcon build, rosdep install) are designed to be deterministic and side‑effect free; they do not keep a history of installed versions because the install space is treated as a mutable directory that users can back up or snapshot externally.Steps for a version‑control‑free rollback (if you are not using an overlay)Before running colcon build, copy the entire install directory to a backup location, e.g. cp -r install install.backup.If the build fails, remove the current install and restore the backup: rm -rf install && mv install.backup install.Optionally, repeat the same for the log and build directories if you want a clean state.If you are using an overlay workspaceSimply delete the overlay install (or the whole overlay) and source the underlay setup file again; the system will fall back to the previously installed versions.To give a more precise recommendation, are you performing the upgrade inside an overlay workspace or directly in the underlay install space?

Does ROS 2 provide an automatic rollback command after a failed package upgrade?

Goal

1 answer

Answer

Confirmed facts

Likely explanation

Steps for a version‑control‑free rollback (if you are not using an overlay)

If you are using an overlay workspace

Your perspective belongs here.

0 question comments