upon submission of a PR, every Dockerfile that was added or modified for the PR is built; the CI pipeline will only report a passing state if all images could be successfully built (or if no Dockerfile was added/modified for the PR)
upon merging a PR, every Dockerfile that was added or modified for the PR is built and, if successful, pushed to zavolab Docker Hub organization; the CI pipeline will only report a passing state if all images could be successfully built and pushed (or if no Dockerfile was added/modified for the PR)
pushing commits to a feature branch will only trigger the CI pipeline if an open PR for the feature branch exists
adherence to the directory naming scheme (<root_dir>/<tool_name>/<version>/Dockerfile) is crucially important, as Docker Hub repo name and tag name are derived from the tool name and version directory, respectively; this is currently not checked by the logic inside the Travis CI config
a Travis status badge for branch master was added to README.md
branch protection rules for branch master were adjusted such that merging PRs is only possible if the Travis CI pipeline completes successfully
Dockerfilethat was added or modified for the PR is built; the CI pipeline will only report a passing state if all images could be successfully built (or if noDockerfilewas added/modified for the PR)Dockerfilethat was added or modified for the PR is built and, if successful, pushed tozavolabDocker Hub organization; the CI pipeline will only report a passing state if all images could be successfully built and pushed (or if noDockerfilewas added/modified for the PR)<root_dir>/<tool_name>/<version>/Dockerfile) is crucially important, as Docker Hub repo name and tag name are derived from the tool name and version directory, respectively; this is currently not checked by the logic inside the Travis CI configmasterwas added toREADME.mdmasterwere adjusted such that merging PRs is only possible if the Travis CI pipeline completes successfullyCloses #35