Variables

Custom variables let you parametrize how your pipeline works. In every pipeline, Microtica also injects a predefined set of variables such as MIC_PIPELINE_EXECUTION_ID, MIC_USER_NAME, and MIC_COMMIT_REF, which you can use alongside your 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

Add variables when you create or modify a pipeline from the GUI. Environment variables automatically become available in the pipeline runtime environment through standard Unix syntax, ${variable-name}.

The following example uses two custom variables, SONAR_URL and SONAR_LOGIN.

You can reference custom variables and Microtica predefined variables directly in the step parameters. Here, the Docker image tag is set to 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

Because the SONAR_LOGIN variable is marked as sensitive, its value is stored encrypted and decrypted securely only within the step execution boundary.

Predefined variables

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

Next steps

• Pipeline syntax reference
• Pass input parameters to steps
• Clone a repository with the git-clone step