-
Bug
-
Resolution: Duplicate
-
Minor
Currently, if a user tries to run a parametrised pipeline job or freestyle, it will likely not work as it will run the job without any mandatory parameters.
In Scope:
- Blue ocean should detect a parametrised job and the RUN button redirect to the run form on classic (at least until blue ocean supports setting of parameters).
Out of scope:
- A blue ocean form screen to capture these parameters.
Multibranch pipeline jobs are currently no parametrised so supporting trigger parameters is a lower priority for blue ocean, but given existing popularity of parametrised jobs, it seems wrong to just "break" them.
- duplicates
-
JENKINS-38393 DESIGN: Capturing of build parameters for parametrised builds
-
- Resolved
-
[JENKINS-36937] Detect parmetrised jobs and redirect to classic
michaelneale I'd rather just support parameterised jobs. Let me chew on this.
jdumay me too - but its a fair bit of work to build dynamic forms. Ideally would reuse the same work as input step for pipeline (in theory, very similar in concept).
Its super powerful and popular, but a lot of work to get right. I think post 1.0 IMO as parametrised is not yet in multibranch.
jamesdumay this came via twitter, and I think it is a legit bug to address (and not too much work).