At the moment we are facing issues with a certain GitLab CI Runner (hifis-runner-manager-1) that execute your GitLab CI pipelines. We are working on it to bring them back to service again. Please excuse the inconveniences.

Commit f06dc438 authored by Hueser, Christian (FWCC) - 138593's avatar Hueser, Christian (FWCC) - 138593 Committed by Hueser, Christian (FWCC) - 138593
Browse files

Renamed environment variables

Used a new ste of environment variable values in gitlab ci yaml file.
parent b41297b0
......@@ -50,7 +50,7 @@ pages:
team_map:
stage: after_deploy
script:
- "HEADERS=\'{\"token\":\"'\"${TOKEN_TRIGGER_GITLAB_CI_SETUP}\"'\", \"ref\":\"gitlab_ci_setup_production\"}\'; curl -X POST -H \"Private-Token: ${MY_PERSONAL_ACCESS_TOKEN_API}\" -H \"Content-Type: application/json\" -d \"$HEADERS\" https://gitlab.hzdr.de/api/v4/projects/960/trigger/pipeline"
- "HEADERS=\'{\"token\":\"'\"${VAR_TRIGGER_TOKEN_FOR_MULTI_PROJECT_PIPELINE}\"'\", \"ref\":\"gitlab_ci_setup_production\"}\'; curl -X POST -H \"Private-Token: ${VAR_MY_PERSONAL_ACCESS_TOKEN_FOR_API}\" -H \"Content-Type: application/json\" -d \"$HEADERS\" https://gitlab.hzdr.de/api/v4/projects/960/trigger/pipeline"
extends:
- .artifacts_extension
- .only_extension
......
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