I looked at the way micro_ros_platformio handles CI, and saw that they use a separate action to install PlatformIO on the CI runners. I copied this action into this repository and changed the workflow to use it. This fixed the CI build failure for Rolling, sped up the build time, and simplified the workflow structure.
I know the following command will fail, but @grassjelly not sure how else to signal backport intent.
@mergify backport humble galactic foxy
* [#75 Fix CI by using separate action to install PlatformIO environment (backport #73)](https://github.com/linorobot/linorobot2_hardware/pull/75) has been created for branch `humble`
* [#76 Fix CI by using separate action to install PlatformIO environment (backport #73)](https://github.com/linorobot/linorobot2_hardware/pull/76) has been created for branch `galactic`
* [#77 Fix CI by using separate action to install PlatformIO environment (backport #73)](https://github.com/linorobot/linorobot2_hardware/pull/77) has been created for branch `foxy`
Use action from micro_ros_platformio to install PlatformIO in workflow runner.
Removes hacky and problematic workarounds from workflow (manually messing with
.platformio
andpenv
, python install).Fixes #72 Rolling firmware failing to build in CI when installing micro_ros_platformio dependency.
I traced the issue back to https://github.com/micro-ROS/micro_ros_platformio/pull/108 in that project.
I looked at the way micro_ros_platformio handles CI, and saw that they use a separate action to install PlatformIO on the CI runners. I copied this action into this repository and changed the workflow to use it. This fixed the CI build failure for Rolling, sped up the build time, and simplified the workflow structure.
I know the following command will fail, but @grassjelly not sure how else to signal backport intent. @mergify backport humble galactic foxy