setup-ros icon indicating copy to clipboard operation
setup-ros copied to clipboard

Detect and use latest binary releases on Windows & macOS

Open christophebedard opened this issue 4 years ago • 3 comments

Description

We currently hardcode paths to Windows binary release archives and have to update the paths manually when new distros/distro patches are released: https://github.com/ros-tooling/setup-ros/blob/c4e8165ee5518c04dc4588bff7c1028ccf563e6f/src/setup-ros-windows.ts#L9-L17

setup-ros could try to automatically detect and use the latest binary release for a given distro.

Related Issues

This feature request includes macOS assuming that this related feature is implemented: #107

Completion Criteria

  • latest binary releases are automatically fetched and used

Implementation Notes / Suggestions

See https://github.com/ros-tooling/setup-ros/pull/450#issuecomment-928146113

We could fetch releases using the GitHub API and check the tags. The tag format is always release-$DISTRO-YYYYMMDD. Then we check the assets and pick the one for a given platform. This part might be a bit trickier, but it should work.

Testing Notes / Suggestions

christophebedard avatar Sep 28 '21 13:09 christophebedard

Would you consider also adding support for "rolling" by grabbing the latest nightly artifacts from ci.ros2.org? Namely:

  • https://ci.ros2.org/view/packaging/job/packaging_windows/
  • https://ci.ros2.org/view/packaging/job/packaging_osx/

They are technically ahead of Rolling, since they are the latest from-source builds.

jacobperron avatar Oct 22 '21 17:10 jacobperron

Oh yeah that's a good idea!

They are technically ahead of Rolling, since they are the latest from-source builds.

if it's the only way to get Rolling binaries for those platforms, it's fine. We can just document it.

christophebedard avatar Oct 22 '21 19:10 christophebedard

Also, we should note that those artifacts I linked are only for the "core" packages listed in this repos file.

jacobperron avatar Oct 28 '21 03:10 jacobperron