You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would involve a new dedicated github action workflow, which would trigger build / test / deploy images on DockerHub. @sjcqs Do you have any idea how we should tag those images?
We should investigate how to add deploy capacity to ci.sh. It would probably involve secrets stored on github, for a dockerhub user / token.
The text was updated successfully, but these errors were encountered:
We could also version the images, but this would require to either add manual tag to release a version (or use github version) or add sementic in the commit title/description (bugfix, feature, BREAKING CHANGE) to auto-compute the version name.
So image names may look like this: fabernovel/android:api-29-latest (updated by any push on master) fabernovel/android:api-29-v1.0.0 (semantic versioning for release through tag) fabernovel/android:api-29-snapshot (uploaded by any push on develop)
This would involve a new dedicated github action workflow, which would trigger build / test / deploy images on DockerHub. @sjcqs Do you have any idea how we should tag those images?
We should investigate how to add deploy capacity to
ci.sh
. It would probably involve secrets stored on github, for a dockerhub user / token.The text was updated successfully, but these errors were encountered: