saros-project / dockerfiles Goto Github PK

The current deployment workflow is:

• Create image locally and tag them
• Test them locally
• Push images to Docker Hub
• Push changes to GitHub
• Travis verifies whether the image can be build
• Review PR

This workflow has the disadvantage that it is not clear which state is available in GitHub.
The ideal workflow (release by travis after a PR is merged) is not possible, because it is not possible to trigger Travis CI jobs if a PR is merged to master.

The alternative is to build images with a reference to a git commit.
MicroBadger also supports to create a badge that can be integrated in the GitHub Readme and the Docker Hub Readme. This could be used for each tagged version. Furthermore the tags should be part of the build script.

The workflow for the dockerfiles repo changed:

• The images are created automatically during build
• An image is tagged in the remote server if a git tag is pushed

These information are missing the README