Pre-populate parameter names in "Run Pipeline" feature | Feature Requests

Pre-populate parameter names in "Run Pipeline" feature

complete

Jenny Miggin

When using the "Run Pipeline" feature, the name of the parameter is currently left blank, and open to incorrect use. It would be useful to pre-populate this with a list of parameters that have been defined within the config file.

November 9, 2021

Laureen Ma

marked this post as

complete

Laureen Ma

Pre-populating pipeline parameters is now available for organizations that integrate with GitHub App, GitHub OAuth App, Bitbucket Cloud, and Bitbucket Data Center.

For more information or to share feedback, visit our community forum

Sebastian Lerner

FYI, this has been scaled down temporarily while we fix a minor bug. We'll update here when this is rolled back out.

Sebastian Lerner

This has been rolled back out, let us know if you run into any issues.

Sebastian Lerner

Merged in a post:

Provide available parameters for pipeline trigger

Jerry Devin

While triggering a pipeline from the circleci console, it will be nice to have the available deployment parameters being shown in the console to pick from.

November 12, 2024

Laureen Ma

We're currently working on enabling the ability to pre-populate pipeline parameters and would love to get your feedback on the design.

For all auto-populated parameters, you'll be allowed to edit the value but the parameter type and name will be fixed.
If your parameter type is an enum or boolean, you'll be able to select the value from the dropdown.
If the parameter is required, instead of a "trash" icon, an info icon will let you know that this parameter is required (shown in the screenshot).
If the parameter has a default value, we'll pre-populate the default value for you.
If the parameter description is present in the config, we'll display it under the parameter.
To add a new parameter, you would click the '+ Add' button and input the parameter type, name, and value on your own (shown in the first row of the Parameters section).

Does this design meet your expectations when manually running a pipeline? Please share your feedback so we can work to improve this experience.

Alex Sheppard

Laureen Ma Hi, so there's no dropdown for the parameter names? i.e. you still have to remember from memory what the names are from the config?

Nathan

Laureen Ma One problem left for our team is the noise this would put on some pipelines. On pipelines where there are lots of parameters but only a small number are intended to be changed when running manually it'll be difficult to quickly identify which ones to change. It would be beneficial to be able to control which parameters are visible/auto-populated or control the order the parameters appear in.

Nicholas Shaw

Laureen Ma works for our needs

Alex Sheppard

Laureen Ma Since yesterday I've had a new dialog experience. 
There are more steps to get to the parameters now, I need to select a pipeline even if there's only 1! Can this be streamlined?
Secondly, the browser used to offer past values for the parameter name and value text boxes. This is no longer the case, so I'd say the experience has gotten worse.

Laureen Ma

Alex Sheppard An update will be available soon that defaults to the single pipeline and restores the ability to select previous parameter inputs.

Sebastian Lerner

Merged in a post:

Improve trigger pipeline UI

Skent

It is time consuming and error prone to have to find the names of parameters for triggering a pipeline. It would be nice if it discovered the parameters instead. Also for boolean parameters could we just have a checkbox, rather than having to select true/false!

October 24, 2024

Laureen Ma

marked this post as

under review

Nathan

Currently using circle ci for CICD, but still using Jenkins for most other automation tasks specifically because this feature is missing.

Wilfried Goesgens

We at ArangoDB would like to have the complete set of parameters pre-filled with defaults from the

config.yml

with possibly drop downs, so you can choose which params to alter in contrast to the default.

Nathan Fish

Merged in a post:

Dropdown menu for Enum Parameters in Pipeline Trigger

Daniel Bollom

Users would find it easier if the system could identify an enum parameter in the

config.yml

file and display these enum parameters as a dropdown menu, rather than a text box, in the pipeline trigger modal.

This enhancement would streamline the pipeline initiation process, making it more user-friendly. By presenting enum parameters as a dropdown menu, we could reduce potential input errors. Additionally, this change would increase efficiency by saving users' time when triggering pipelines.

August 3, 2023

Nicholas Shaw

Adding upvotes for Agero, even just placeholder text or some sort of informational text that can provided to help the end-user do things the right way would be great

→