We are currently migrating pipelines from Jenkins to gitlab. In jenkins we have groovy script to load variables using drop down feature when we trigger pipeline.
how do we use same feature in gitlab to get a dropdown to select variables while triggering pipeline
is it possible to load the variables through a file or script to have the values populated in when we trigger pipeline manually in gitlab
Appreciate any assistance/ guidance on getting variables populated in gitlab pipeline UI. This is a blocker for us to migrating to gitlab
Thanks @gitlab-greg. this is make and break to migrate from jenkins to gitlab as we have decent number of pipelines which dynamically populate variables. having hardcoding root variables with options is not the best approach for us considering the number of pipelines we have
The same problem, we are also investigating some paths to move away from ancient Jenkins
The inability to customise the UI is one of the biggest problems.
We have one of the jobs - called Matrix Deployment which allows to deploy any service (or even all of them or some of them) at the same time to a specific Kubernetes nspace (or even to all nspaces)
It has dependencies on previous UI element selections and finally, it populated dropdowns with docker versions which are queried directly from ECR (AWS Docker Registry).
So static pre-set values are not gonna help, we need the ability to define some logic behind UI elements, and UI elements need logic to be dependant on previous UI elements
