Skip to content

Add new CI variable for releases

What does this MR do and why?

Adds CI variable CI_RELEASE_NAME.

Related to !98447 (merged) where the variable CI_RELEASE_DESCRIPTION has been created.

The release name cannot be empty, whilst the description can. This creates an easy way to make a pipeline trigger only on a release.

How to set up and validate locally

  1. Use the following simple CI configuration to a test project in local and create a release and run pipeline for the corresponding release tag.
image: alpine:latest

stages:
  - test

prod:
  stage: test
  script:
    - echo "Release name is $CI_RELEASE_NAME"
  1. The job logs should include the variable message being printed when echoed.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

  • I have evaluated the MR acceptance checklist for this MR.
    • Documentation :
      • I have added a changelog trailer since the original MR added one
      • I don't know where is the documentation so if someone would be kind enough to tell me I could update it.
Edited by galyfray

Merge request reports

Loading