-
New Feature
-
Resolution: Duplicate
-
Critical
-
None
When job parameters are defined in the Jenkinsfile/script, Jenkins doesn't know what parameters are required until the job is run. You see the problem? to run the job you need the parameters. To know what parameters are required to run the job.
This is most visible with a new branch in multibranch jobs (there have been complaints).
In scope:
- Investigate if it is possible to know without executing what parameters will be required
- If possible, an api to return such parameters
This could span general pipeline script, or pipeline model.
- duplicates
-
JENKINS-41929 Offer "Build with Parameters" on first build when declarative Jenkinsfile found
-
- Open
-
- relates to
-
JENKINS-40631 first build fails because of missing parameter
-
- Closed
-
hrm ok.. this may have to sit in the backlog for a while.
So whilst PR#60 helps with error message, it is still a broken UX that pops up for the wrong things... so we may need to park this for some future work to make it work out ahead of time what the params are via some kind of evaluation... I don't think this is a problem specific to declarative, and perhaps declarative shouldn't solve it?
EDIT: I am prepared to park this and then let things come in as bug reports... more thought is needed ...