Skip to content
Snippets Groups Projects
Commit 8baccd31 authored by Prada Sarasola, Miguel's avatar Prada Sarasola, Miguel
Browse files

Explicitly point to legacy branch of industrial_ci

This is the most conservative approach, and allows us to switch to
master only when we explicitly decide to do so.
parent 3ad7f34a
Branches
No related tags found
1 merge request!31Use the recommended way of cloning the industrial_ci repo - and explicit branch name
Pipeline #18211 passed
......@@ -19,7 +19,7 @@ before_script:
stage: build
before_script:
- apk add --update bash coreutils tar
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .ci_config -b master
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .ci_config -b legacy
- docker login ${ARTIFACT_DOCKER_URL} -u ${ARTIFACT_CI_USER} -p ${ARTIFACT_CI_TOKEN}
script: .ci_config/gitlab.sh
variables:
......
......@@ -19,7 +19,7 @@ before_script:
stage: build
before_script:
- apk add --update bash coreutils tar
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .ci_config -b master
- git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci.git .ci_config -b legacy
- docker login ${ARTIFACT_DOCKER_URL} -u ${ARTIFACT_CI_USER} -p ${ARTIFACT_CI_TOKEN}
script: .ci_config/gitlab.sh
variables:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment