Enhancements on the list the deployments related to a release

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Release notes

Currently the List the deployments related to a release is able to link only if the deployment is released from a Git Tag pipeline.

Also if there are multiple deployments to multiple environments in the same release pipeline (for instance if the same pipeline deploys to Staging and Production environments, or if the pipelines deploy multiple components, for instance in a monorepo setup), all of them are linked to the release, and it is not possible to restrict to show only the relevant deployments (for instance only the production deployments or only specific components deployments).

Problem to solve

As a release manager, I want more flexibility in how to link deployments and releases, so I can tweak the options to see the relevant deployment information from releases.

Intended users

Rachel (Release Manager)

Proposal

GitLab should provide an optional better way to link deployments to releases. Currently deployments are automatically linked based on the pipeline ref. We should have an optional configuration to the .gitlab-ci.yml file in order to be able to override the ref, so that we can link the deployments to related releases in a better way.

environment:
  ref: <custom_ref for instance $CUSTOM_TAG>

That would provide much more flexibility to link deployments to releases and would cover much more use-cases.

Further details

Typical use cases would be projects running releases from no-TAG pipelines or within complex pipelines with multiple deployments, for instance in monorepo projects. This will enable the current feature for this kind of projects.

Edited Sep 22, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading