Skip to content

Use dynamic management of pipeline variables

Description

We have a few places where we can specify secret variables for pipelines, and we are going to add even more (https://gitlab.com/gitlab-org/gitlab-ce/issues/35896).

Since "old" way to pass variables is a pain if you need to add more than one (click on save, page refresh, scrolling to top), we should move to the new dynamic one.

Proposal

Use what we already have in CI/CD > Schedules everywhere (at the moment, CI/CD > Settings).

Differences are that here we also have protected flag and environment scope field (for "EE Premium"/"EE Ultimate".

Design

  • Display an enabled save button when there is an edit, otherwise make the button disabled.
  • The Environment scope field becomes hidden on CE and non licensed and ~"EE Starter" versions.

image

Links / references

Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/38504.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/35896.

Documentation blurb

Overview

What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?

Use cases

Who is this for? Provide one or more use cases.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

Edited by Eric Eastwood