This PR adds a workflow that wraps the two workflows (multi arch build-push and write file) from our .github repository for the particular case of our docker-images. In other words, this translates - with minor differences - the build-push action into a workflow, such that we are able to reuse other workflows from other places.
While we still have that special parsing of inputs that can get the Dockerfile path and workspace directory from the image names (ros2_control_libraries with branch develop if you want to build ros2-control-libraries:humble-devel etc.) we have the special case of the ros2_ws where we need to copy the sshd_entrypoint.sh script. For that, we need to upload the file as an artifact and pass the artifact name and path to the build-push workflow from the .github repo.
I want to show you the new workflow before I delete the existing actions and refactor the current workflows. This has been tested on my fork already.
Description
This PR adds a workflow that wraps the two workflows (multi arch build-push and write file) from our .github repository for the particular case of our docker-images. In other words, this translates - with minor differences - the build-push action into a workflow, such that we are able to reuse other workflows from other places.
While we still have that special parsing of inputs that can get the Dockerfile path and workspace directory from the image names (
ros2_control_libraries
with branchdevelop
if you want to buildros2-control-libraries:humble-devel
etc.) we have the special case of theros2_ws
where we need to copy thesshd_entrypoint.sh
script. For that, we need to upload the file as an artifact and pass the artifact name and path to the build-push workflow from the .github repo.I want to show you the new workflow before I delete the existing actions and refactor the current workflows. This has been tested on my fork already.
Review guidelines
Estimated Time of Review: x minutes