From 451e897b000a91f0b426c05dae3580e55237a745 Mon Sep 17 00:00:00 2001 From: Artem Hluvchynskyi Date: Sat, 2 Feb 2019 01:40:42 +0200 Subject: [PATCH] Fixes Docker Hub repository tag env var name As noted in issue #6684 `CACHE_TAG` environment variable is actually empty in the builds, turns out the documented value is represented by a `DOCKER_TAG` variable instead. --- docker-hub/builds/advanced.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-hub/builds/advanced.md b/docker-hub/builds/advanced.md index 81e57207b9..bf89e5c4e6 100644 --- a/docker-hub/builds/advanced.md +++ b/docker-hub/builds/advanced.md @@ -22,8 +22,8 @@ processes and do not affect your service's run environment. * `COMMIT_MSG`: the message from the commit being tested and built. * `DOCKER_REPO`: the name of the Docker repository being built. * `DOCKERFILE_PATH`: the dockerfile currently being built. -* `CACHE_TAG`: the Docker repository tag being built. -* `IMAGE_NAME`: the name and tag of the Docker repository being built. (This variable is a combination of `DOCKER_REPO`:`CACHE_TAG`.) +* `DOCKER_TAG`: the Docker repository tag being built. +* `IMAGE_NAME`: the name and tag of the Docker repository being built. (This variable is a combination of `DOCKER_REPO`:`DOCKER_TAG`.) If you are using these build environment variables in a `docker-compose.test.yml` file for automated testing, declare them in your `sut`