Skip to content

Handle empty release description in CI variables builders

Bala Kumar requested to merge 377872-fix-regression-bug into master

What does this MR do and why?

Handles empty release description while building the CI_RELEASE_DESCRIPTION variable.

Regression introduced from !98447 (merged)

Screenshots or screen recordings

regression_fix

How to set up and validate locally

  1. Create a release without description in local. Example
curl --header 'Content-Type: application/json' --header "PRIVATE-TOKEN: <your_access_token>" \
     --data '{ "name": "New release", "tag_name": "v0.3" }' \
     --request POST "https://gitlab.example.com/api/v4/projects/24/releases"
  1. Run pipeline for the tag v0.3 with the below CI config
image: alpine:latest

stages:
  - test

prod:
  stage: test
  script:
    - echo "Release description is $CI_RELEASE_DESCRIPTION"
  1. Job should be successful.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #377872 (closed)

Edited by Bala Kumar

Merge request reports