At the moment we published to dockerhub with the TAG:latest, there should be at least one other tag with a version number.
We can choose what ever version numbering scheme we wanted, a simple versioning scheme is just the date e.g. yyyy.mm.dd
Add restrictions on actions to allow the "build latest image" job to run only if there are changes in the Dockerfile or entrypoint.sh in the main branch.
Create another job to push the image to the GitHub registry for test builds (validation images / release candidates).
Build only if there are some modification on docker-compose and entrypoint files : Sort out the labelling and publishing only changed image.
That mean, we'll need to figure out how to get the github runner to only publish the image template that had changes.
For example: change to the SSHLibrary template should no cause a new rfswarm-agent-base-image to get published
Improvement to add for the agent:
At the moment we published to dockerhub with the TAG:latest, there should be at least one other tag with a version number.
We can choose what ever version numbering scheme we wanted, a simple versioning scheme is just the date e.g. yyyy.mm.dd
Add restrictions on actions to allow the "build latest image" job to run only if there are changes in the Dockerfile or entrypoint.sh in the main branch.
Create another job to push the image to the GitHub registry for test builds (validation images / release candidates).
Build only if there are some modification on docker-compose and entrypoint files : Sort out the labelling and publishing only changed image. That mean, we'll need to figure out how to get the github runner to only publish the image template that had changes. For example: change to the SSHLibrary template should no cause a new rfswarm-agent-base-image to get published
~Clean github registry after success merge~
Push on github registry for every branches