Hello,
Is there a way to make manual build step ask for input parameters.
I need to update deployment step to support deployment of specific build , not the latest one that was build.
If I trigger it via api, I can supply a variable.
Is there a way to prompt for the variable value when initiating manual build step from gitlab web ui ?
1 Like
Highly interested as well.
is manual pipelines working?
This is indeed a feature that would be very useful. +1
1 Like
Agree, this feature would be very useful!
+1
I need it, I want it !
Vote for it : https://gitlab.com/gitlab-org/gitlab-ce/issues/32003
+1
I need it, I want it !
1 Like
yep, but you have to know variable names somehow. We want to define (in the pipeline) needed variable names and/or pre-defined values (dropdown) to set, default values.
3 Likes
This would be a great feature where you could setup the variables to set and make it like a form similar to build with parameters pipeline setup in Jenkins.
@sharkymcdongles Please add your thoughts to these feature requests, and maybe add a screenshot from Jenkins to clarify 
Meanwhile I’ve linked this topic there.
@dnsmichi Basically something similar to this:
Use case is it would allow for creating essentially a form to allow non techy people to run super complex builds they otherwise would be unable to touch.
4 Likes
Do we have any update on this implementation.
Hi,
this was released in GitLab 13.7: GitLab 13.7 released with merge request reviewers and automatic rollback upon failure | GitLab
Cheers,
Michael
1 Like
@dnsmichi ,
I saw the masked variable on GitLab 13.7 released with merge request reviewers and automatic rollback upon failure | GitLab
any idea on how to add a masked variable ?
- tried to mask PASS and AWS_SECRET_ACCESS_KEY on Settings > CI/CD > Variables
but without success
variables:
USER:
value: "username"
description: ""
PASS:
value: "!passwordtestalsdjfl"
description: ""
AWS_SECRET_ACCESS_KEY:
value: "hiddenpassword123"
description: ""
get_vars:
script:
- export
when: manual