I use
include:
- component: $CI_SERVER_FQDN/$CI_PROJECT_PATH/gitlab-ci-releasemanagement@$CI_COMMIT_SHA
inputs:
stage: release
stages:
- release
# If we are tagging a release with a specific convention ("v" + number) and all
# previous checks succeeded, we proceed with creating a release automatically.
create-release:
stage: release
image: registry.gitlab.com/gitlab-org/release-cli:latest
rules:
- if: '$CI_COMMIT_TAG =~ /^\d+\.\d+\.\d+$/'
script: echo "Creating release $CI_COMMIT_TAG"
release:
tag_name: "${CI_COMMIT_TAG}" # "v${CI_COMMIT_TAG}"
description: "Release of ${CI_PROJECT_NAME} version ${CI_COMMIT_TAG}"
The release is created for the version tag. All is OK
“After the release job completes successfully, the release is created and the new version
is published to the CI/CD catalog.”
but publish a new version of the component to the catalog: NO GENERATES NOTHING
Log
$ echo “Creating release $CI_COMMIT_TAG”
Creating release 0.1.71
Executing “step_release” stage of the job script
00:00
$ release-cli create --description “Release of releasemanagement version 0.1.71” --tag-name “0.1.71”
time=“2024-08-23T11:18:10Z” level=info msg=“Creating Release…” catalog-publish=false cli=release-cli command=create name= project-id=122 ref=0fcb3056853f3b0f33fefafd23be47f5ce3a79e3 server-url=“https://gitlab.xxx.es” tag-message= tag-name=0.1.71 version=0.18.0
Tag: 0.1.71
Name: 0.1.71
Description: Release of releasemanagement version 0.1.71
Created At: 2024-08-23 13:18:10.525 +0200 +0200
Released At: 2024-08-23 13:18:10.525 +0200 +0200
See all available releases here: https://gitlab.xxx.es/zzz/devops/ci-components/releasemanagement/-/releases
time=“2024-08-23T11:18:10Z” level=info msg=“release created successfully!” catalog-publish=false cli=release-cli command=create name= project-id=122 ref=0fcb3056853f3b0f33fefafd23be47f5ce3a79e3 server-url=“https://gitlab.xxx.es” tag-message= tag-name=0.1.71 version=0.18.0
Cleaning up project directory and file based variables
00:01
Job succeeded