Clarify container naming
This commit is contained in:
parent
e8ae17a880
commit
020089b33a
@ -27,11 +27,11 @@ Given a registry user `$USER`, every run of this script will do the following fo
|
||||
* For each container `$CONTAINER` to build from this repository:
|
||||
* `cd` into the relative path
|
||||
* Build the container using the specified Dockerfile
|
||||
* Push the image as `$USER/$REPO:$COMMIT_SHA`
|
||||
* Push the image as `$USER/$REPO:bleeding`
|
||||
* Push the image as `$USER/$REPO-$CONTAINER:$COMMIT_SHA`
|
||||
* Push the image as `$USER/$REPO-$CONTAINER:bleeding`
|
||||
* If the ref is a tag
|
||||
* Push the image as `$USER/$REPO:$TAG`
|
||||
* Push the image as `$USER/$REPO:latest`
|
||||
* Push the image as `$USER/$REPO-$CONTAINER:$TAG`
|
||||
* Push the image as `$USER/$REPO-$CONTAINER:latest`
|
||||
|
||||
Pretty straightforward, pretty intuitive. Every build updates `:bleeding`, tags update `:latest`.
|
||||
|
||||
|
@ -6,7 +6,7 @@
|
||||
repo_branch: "main"
|
||||
repo_build_tags: true
|
||||
containers:
|
||||
5dd_client:
|
||||
client:
|
||||
path: "client"
|
||||
5dd_server:
|
||||
server:
|
||||
path: "server"
|
||||
|
Loading…
x
Reference in New Issue
Block a user