if condition variables in gitlab-ci.yml

Question

I have a simple request but can't find any sample code for it.

Suppose I want to set an environment variable depending on the branch name. Something like this (though I know this code doesn't work)

variables:
  rules:
    - if: '$CI_COMMIT_BRANCH != "master"'
      variables:
        env: "dev"
    - if: '$CI_COMMIT_BRANCH == "master"'
      variables:
        env: "prod"
  stackName: projectA-${env}

So the stackName or other variables can use ${env} as suffix in the name and I can also use ${env} in jobs , scripts or stages

How can I set it?

Answer 1

The variable env or stackName can be set in two different job, which run with a rule according the branch. And you can define a template job, to make same thing for both environment. For example, define two jobs like this with a template :

.template-job:
  script:
    - echo $STACK_NAME

prod-job:
  variables:
    STACK_NAME: projectA-prod
  rules:
    - if: '$CI_COMMIT_BRANCH == "master"'
  extends: .template-job

dev-job:
  variables:
    STACK_NAME: projectA-dev
  rules:
    - if: '$CI_COMMIT_BRANCH != "master"'
  extends: .template-job

Using this, you have two jobs but they extends the same template-job, which is using the variable $STACK_NAME. You can of course name it ENV or whatever.

Answer 2

You can use it in this way.

  environment:
    name: your-env-dev
  rules:
    - if: '$CI_COMMIT_REF_NAME == "master" && "your-env-dev" =~ $YOUR_INSTANCES'

Set the variable value in settings under CI/CD

Answer 3

Answer my question after about 1 year. Here is my solution, and a simple solution.

I refered the idea from @Time recommended.

gitlab pipeline's environments are similar concept of CircleCI's context , if you are familar it.

• create environments first, such as develop, staging, production, etc
• create variables but assigned to different environments

• you can set the variables with same names, but assigned to different environments.

When use it, you can add below codes to each task

staging_build:
  stage: build
  environment:
    name: staging
  script:
    - echo ${AWS_ACCESS_KEY_ID}
  only:
    - staging

production_build:
  stage: build
  environment:
    name: production
  script:
    - echo ${AWS_ACCESS_KEY_ID}
  only:
    - main

Answer 4

You can do likely this in the workflow section.

variables: 
  stackName: projectA-${env}

workflow:
  rules:
   - if: '$CI_COMMIT_BRANCH == "master"'
     variables:
       env: prod
   - when: always # only evaluates this if the above was false
     variables:
       env: dev

For long and complicated sets, I'd put them in separate files and include them.

include: branch_config/$CI_COMMIT_BRANCH.yaml