I'm pretty sure that doesn't exist at the moment, or I at least don't know of a direct analogue of what you refer to on the ROS 1 wiki. (Edit: would perhaps make for a nice contribution: the information is all there).
An alternative, but somewhat different, could be repo.ros2.org/status_page. These are also linked from the Resources section in the Humble Ubuntu installation documentation.
Those pages are periodically updated by the ROS 2 buildfarm, and provide basically the same information as the list you refer to on the ROS 1 wiki, but in a different format.
The names of the pages correspond to the platform/OS a particular ROS 2 version supports and gets packages built for. For Humble fi, there are:
If you open the first one, and filter for rclcpp
, you get this page:
![image description](/upfiles/16849596074561402.jpg)
The links to the buildfarm jobs are "hidden" in the last two columns: Jsource
and J64
. That would be the source jobs and the amd64
binary jobs respectively. The squares can have different colours than green, and the page has a legend for what those other colours would mean which I won't duplicate here.
The first square in each column links you to a job. For rclcpp
that would be:
For other supported platforms/OS, you'd have to open the other pages under repos.ros2.org/status_page
.
Or perhaps you could navigate to the source job and check what Downstream Projects exist:
![image description](/upfiles/16849600815013534.jpg)
As yet another alternative: that same host also serves .yaml
files which contain the same/similar information: repo.ros2.org/status_page/yaml. For rclcpp
in ros_humble_default.yaml
:
rclcpp:
build_status:
ubuntu:
jammy:
amd64:
build: 16.0.4-2jammy.20230426.055957
main: 16.0.4-2jammy.20230426.055957
test: 16.0.4-2jammy.20230426.055957
source:
build: 16.0.4-2jammy
main: 16.0.4-2jammy
test: 16.0.4-2jammy
maintainers:
...
This doesn't link to any jobs per se, but if your question is really just:
How can I see what binaries are available for a ROS2 package?
combining the information from all three .yaml
s for Humble would seem to answer that.