This PR automates the process of pushing Docker images with latest tag upon each merge to the development branch. It accomplishes this by storing the images generated during the execution of the test-image target using the https://github.com/actions/upload-artifact action and subsequently downloading and pushing them to the repository following the completion of testing.
It also changes ray docker images to have a base image and thus avoids the need to call update_dockerfile.sh script to update the ray version in set-versions.
Why are these changes needed?
This PR automates the process of pushing Docker images with
latesttag upon each merge to the development branch. It accomplishes this by storing the images generated during the execution of thetest-imagetarget using thehttps://github.com/actions/upload-artifactaction and subsequently downloading and pushing them to the repository following the completion of testing. It also changes ray docker images to have a base image and thus avoids the need to call update_dockerfile.sh script to update the ray version in set-versions.Related issue number (if any).
https://github.com/IBM/data-prep-kit/issues/176