Triggered Pipeline Ambiguity

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

  • Close this issue

Currently, we are building source code in "Build" repository and trigger "Deploy" repository to create deploy jobs.

We noticed that when we trigger Build repository and pipeline is created in Deploy repository, its Commit ID and Commit Message will be the same as previous one. That confuses developers because they cannot know which trigger created which job. If there was a way to send Commit Message of Build repository's trigger job, or a way to configure and send a Commit Message to be shown in curl request, it'd be helpful.

Currently, our curl call is like this:

curl -s --request POST --form token=$TRIGGER_TOKEN --form ref=master --form "variables[IMAGE_TAG]=snapshot-${CI_COMMIT_SHA:0:8}" https://example.gitlab.com/api/v4/projects/${PROJECT_ID}/trigger/pipeline

Is there any solution to this already? If not, I'd like to request it.

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