Pipeline triggered by "Run Pipeline" does not show extra variables

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

• Close this issue

Problem to solve

There is no UI that would tell me that the running pipeline I'm looking at was triggered manually with extra variables.

We have two projects - backend and webapp

• backend runs build and publishes docker images that contain the application
• webapp contains end-to-end tests, that use the backend images (it pulls them, start the backend containers and execute the tests against them)
• webapp is also parametrized and runs the tests against the docker image tag master, but it can be changed by specifying BACKEND_CI_COMMIT_REF_NAME variable
• because there is no UI that would tell me, that the pipeline/job I'm looking at was executed with extra variable BACKEND_CI_COMMIT_REF_NAME=fp-some-feature it is very hard to find this info (I have to dig into job logs)

I know the variables are listed when I use trigger pipeline using trigger token, but IMHO they should also be listed, when triggered manually.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)

Proposal

Extra variables should be listed in the pipeline (and probably also job) details.

The variables should also have a toggle (as they have in CI settings) to indicate that the value is secret - in that case, just the variable name would be listed, not it's value.

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

I can determine easily, that the pipeline was not triggered by a git push, but by manually submitting "run pipeline" (or by api call) and mainly - I can also see the extra variables which helps me understand why.