Read about our upcoming Code of Conduct on this issue

Commit 89febf78 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Kaniko: using --force option to bypass check of running in container

See heptapod/heptapod-runner#24
for explanations.
parent dafb63edf584
Pipeline #27392 failed with stages
in 4 minutes and 4 seconds
......@@ -50,6 +50,7 @@ if [ "$HG_VERSION" = "stable" ]; then
/kaniko/executor --context $CI_PROJECT_DIR/context \
--dockerfile $CI_PROJECT_DIR/Dockerfile.rolling-hg \
--force \
--build-arg HG_BRANCH=${HG_VERSION} \
--build-arg PYDEPS_TAG=${PYDEPS_TAG} \
--single-snapshot \
......@@ -61,6 +62,7 @@ elif [ "$HG_VERSION" = "default" ]; then
/kaniko/executor --context $CI_PROJECT_DIR/context \
--dockerfile $CI_PROJECT_DIR/Dockerfile.rolling-hg \
--force \
--build-arg HG_BRANCH=${HG_VERSION} \
--build-arg PYDEPS_TAG=${PYDEPS_TAG} \
--single-snapshot \
......@@ -74,6 +76,7 @@ elif [ "$HG_VERSION" = "current" ]; then
# TODO put released hg version to use in a separate file for better clarity
/kaniko/executor --context $CI_PROJECT_DIR/context \
--dockerfile $CI_PROJECT_DIR/Dockerfile.released-hg \
--force \
--build-arg HG_VERSION=5.7.1 \
--reproducible \
--build-arg PYDEPS_TAG=${PYDEPS_TAG} \
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment