You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A workflow that grew out of some user's CICD workflows is to tell abaco deploy to override the value specified by DOCKER_IMAGE_VERSION in the reactor.rc file with the current Git repo short hash.
This is achieved by detecting the hash and passing it to the -t option, but this requires a separate, out-of-band step to detect the hash.
Extend the abaco deploy workflow to support this automatically:
Add DOCKER_USE_COMMIT_HASH as a reactor.rc variable
Add detection of current git commit hash to abaco deploy
Update behavior of -t so the image tag is set in the following order when DOCKER_USE_COMMIT_HASH=1
A workflow that grew out of some user's CICD workflows is to tell
abaco deploy
to override the value specified byDOCKER_IMAGE_VERSION
in thereactor.rc
file with the current Git repo short hash.This is achieved by detecting the hash and passing it to the
-t
option, but this requires a separate, out-of-band step to detect the hash.Extend the
abaco deploy
workflow to support this automatically:DOCKER_USE_COMMIT_HASH
as areactor.rc
variableabaco deploy
-t
so the image tag is set in the following order whenDOCKER_USE_COMMIT_HASH=1
Argument
-t [value]
>[git commit hash]
>latest
if git |DOCKER_IMAGE_VERSION
if ! gitThe text was updated successfully, but these errors were encountered: