`Run Pipeline` should autocomplete or prefill `only` variables in the web UI
Problem to solve
Running a pipeline manually with arguments in variables is manual and error prone. Choices for variable names could be autocompleted (or pre-filled into form elements that can be selected/deselected) based on only: {variables: }
entries in gitlab-ci.yml
.
Further details
The primary use case triggering web
jobs from the UI without having to constantly refer to documentation or the gitlab-ci.yml
to look for required variables and, where specified with ~=
or ==
, provide some minimal checks for what will be run.
UI such as this is available in comparable applications.
Proposal
At a minimum, offer variable names from gitlab-ci.yml
as autocomplete suggestions in the Run Pipeline
UI. If possible, pre-add entries with empty values for only
variables where none would be available by default to the user based on the CI/CD configuration.
What does success look like, and how can we measure that?
More manual development tasks for which schedules or API triggers are inappropriate are being implemented as pipelines. Users are configuring CI/CD to run web
triggered jobs that take variables.
This can be measured with an increase in web
triggered jobs with variables.