Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40241

Detemine parameters before running job

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            This came up in discussion with a CB customer (for Script, but I was discussing that this was more viable to do in Declarative). Apart from schedule, what seems to be the blocker here?

            Show
            jamesdumay James Dumay added a comment - This came up in discussion with a CB customer (for Script, but I was discussing that this was more viable to do in Declarative). Apart from schedule, what seems to be the blocker here?
            Hide
            benjigoldberg Benjamin Goldberg added a comment -

            This is marked as resolved, but by what? Is there an open PR somewhere we can look at? Would love to see this feature in our installation of Jenkins and wondering if its available in the latest release.

            Show
            benjigoldberg Benjamin Goldberg added a comment - This is marked as resolved, but by what? Is there an open PR somewhere we can look at? Would love to see this feature in our installation of Jenkins and wondering if its available in the latest release.
            Hide
            jamesdumay James Dumay added a comment -

            It's duplicated. See the linked tickets for where this is really tracked.

            Show
            jamesdumay James Dumay added a comment - It's duplicated. See the linked tickets for where this is really tracked.
            Hide
            benjigoldberg Benjamin Goldberg added a comment -

            James Dumay I clicked through a number of associated tickets (many of which are duplicated themselves) and I am unable to find the PR that resolves this issue. Any chance we could add the link here as well?

            Show
            benjigoldberg Benjamin Goldberg added a comment - James Dumay I clicked through a number of associated tickets (many of which are duplicated themselves) and I am unable to find the PR that resolves this issue. Any chance we could add the link here as well?
            Hide
            michaelneale Michael Neale added a comment -

            Benjamin Goldberg https://issues.jenkins-ci.org/browse/JENKINS-41929 is ticket. There is no PR I am aware of that fixes this. Pipeline being scripted by default (outside of `pipeline`) makes this impossible in a sense (ie need to execute it before you know what parameters are used). Declarative has a chance that this can be elided pre-flight. 

            Show
            michaelneale Michael Neale added a comment - Benjamin Goldberg https://issues.jenkins-ci.org/browse/JENKINS-41929  is ticket. There is no PR I am aware of that fixes this. Pipeline being scripted by default (outside of `pipeline`) makes this impossible in a sense (ie need to execute it before you know what parameters are used). Declarative has a chance that this can be elided pre-flight. 

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                michaelneale Michael Neale
              • Votes:
                4 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: