Variables

Microtica allows you to define custom variables that can be used to parametrize the way your pipeline works.

In each pipeline, Microtica will automatically inject a predefined set of variables like MIC_PIPELINE_EXECUTION_ID, MIC_USER_NAME, MIC_COMMIT_REF etc. that can be used in conjunction with the custom variables.

Use pipeline variables when you want to:

• parametrize the way your pipeline works
• avoid hard-coding within the step execution logic
• avoid storing sensitive information within the pipeline yaml

Microtica offers two types of variables:

• plaintext variables
• sensitive variables

Adding variables can be done during creating/modifying pipeline from the GUI. Environment variables will automatically became available to use in pipeline runtime environment using a standard Unix syntax ${variable-name}.

Environment variables in Microtica



In the following example, we are using predefined variables SONAR_URL and SONAR_LOGIN.

We can reference a custom as well as Microtica predefined variables directly in the step parameters. In this case, we are setting the tag for the Docker image to be the value of {{MIC_PIPELINE_EXECUTION_ID}}.

steps:
  AnalyseApp:
    image: node:latest
    commands:
      - sonar-scanner -Dsonar.host.url=${SONAR_URL} -Dsonar.login=${SONAR_LOGIN}
  DockerPush:
    type: docker-push
    image_name: microtica/user-service
    tag: "{{MIC_PIPELINE_EXECUTION_ID}}"
    registry: dockerhub

As we marked SONAR_LOGIN variable as sensitive, the value will be stored encrypted and securely decrypted only within the step execution boundary.

Predefined variables

In each step execution, Microtica will automatically inject a set of predefined variables you can use within the pipeline.