Extend 'trigger' syntax - add a possiblitiy to specify a specific (git) tag in bridge jobs

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

• Close this issue

Problem to solve

At the time being only branch may be specified in the bridge job (https://docs.gitlab.com/ee/ci/yaml/README.html#complex-trigger-syntax), but it is quite desirable to allow from tags to make possible to trigger released versions of the downstream pipelines,

Intended users

The most likely users are DevOps and Release Engineers.

Further details

Provides for the better isolation of upstream and downstream pipelines development, allow to use released versions-

Proposal

One of 2 approaches may be used:

1. Add a support for the tag keyd, similar to branch, but accepting tag name instead of branch name
2. Deprecate the branch key and introduce ref key accepting any valid git reference (branch, tag, commit hash, whatsoever), Make sure that branch and ref cannot be used simultaneously in the same job.

As for the 2nd approach is highly preferable as more universal and consistent.

Permissions and Security

No changes

Documentation

Just reflect the changes

Testing

Check that the proper ref is taken.

What does success look like, and how can we measure that?

What is the type of buyer?

As multi-project pipelines and trigger are "Premiun/Silver" this feature should belong to the same tier.

Links / references