show values for pipeline parameters somewhere in IU: worflow page, on Pipelines page etc
O
O Kulychok
We can customize jobs and/or workflows based on pipeleine parameters BUT I cannot see none of those parameters in UI and cannot understand what particular job should do: compile? compile+deploy? compile+test? compile+test+deploy? deploy to instance #1? #2? #3? all of above? And add category "User Interface" to "Ideas"
CCI-I-1616
Paul Garner
I just started writing up a new feature request for this then found this one already here for nearly 5 years 😭 (I can't understand why such a simple and obviously necessary feature hasn't been implemented yet...?)
If I define pipeline parameters in the config then when I "Trigger Pipeline" there is a UI for entering param values.
But AFAICT there is no way to go back and see what param values were chosen on a previously triggered workflow, e.g. https://app.circleci.com/pipelines/github/infomediacode/superservice-analytics/4318/workflows/a9b1c6a9-5a3f-497e-8860-7bac0124e4ac
I would like to be able to see the param values on:
- the workflow page
- the page for jobs executed within the workflow
- ideally also on the branch page, beneath the workflow name or as a tooltip or something
A
Alex Southwell
Would change my life. I have to do hacks by echoing the parameters in a step.
Branden Hamilton
This feature would greatly improve build auditability, i.e. knowing for each triggered build, what parameter values were used. Similarly it would assist in debugging.
I was expecting to find something similar to how Jenkins does this: https://plugins.jenkins.io/show-build-parameters/
Andrea Censi
Yes. It would also be used to expose them via the API.
V
Vinny Thanh
I agree having a nicer, summarized view of all the pipeline parameters would be a useful feature.
But in the interim, you should be able to view what the value of your parameters resolved to by going to a workflow or job details page -> top right ellipses -> Configuration File -> Compiled. We show the original source configuration you committed as well as what the processing "compiles" or resolves to.
J
Joseph Evasco
Vinny Thanh: How about for pipeline parameters like << pipeline.trigger_source >>? this compiled version does not show those values
Merged in a post:
Show pipeline parameters in the UI
S
Steve Sklar
Showing the values of pipeline parameters in the UI would help users identify why a certain job ran according to parameters.This would make following the logic of the pipeline more transparent.
CCI-I-1599