Added tagging logic for debian-base to support both Stretch and Buster build tags. #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Added tagging logic for
debian-base
images to support both Stretch and Buster build tags.debian-base
image as the downstreamdocker-pi-hole
would be affected if the image were immediately cut over to Buster.debian-base:lastest
image.debian-base:latest
(on master - stretch for now)debian-base:stretch
(on master)debian-base:buster
(on master)debian-base:{tag}
(branch doesn't matter - stretch for now)debian-base:{tag}-stretch
(branch doesn't matter)debian-base:{tag}-buster
(branch doesn't matter)debian-base:{branch}
(stretch for now)debian-base:{branch}-stretch
debian-base:{branch}-buster
Want to test this?
docker-compose build
DRY_RUN=true ./tag-and-push.sh {docker-compose service name}
to see what the resulting tags are, example:DRY_RUN=true ./tag-and-push.sh debian-base-stretch
.