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

specifying a cli parameter causes unspecified parameters to be blank

      If you have a parameterized job with multiple parameters, all with default values, you can trigger it via an upstream build and all parameters have the default value as expected. This also works when building it via the CLI if you don't specify parameters.

      However as soon as you specify one parameter like "-p PARAM1=foo" then all the other parameters lose their default value and are blank for the build.

      I would expect that specifying one parameter should still allow others to get the default, otherwise in our scripts that invoke CLI builds, we have to put in every parameter and duplicate the default value which is error-prone and is easy to forget when changing one. Confirmed with a fresh and clean 1.370 Hudson.

          [JENKINS-7162] specifying a cli parameter causes unspecified parameters to be blank

          mcrooney created issue -
          mcrooney made changes -
          Description Original: If you have a parameterized job with multiple parameters, all with default values, you can trigger it via an upstream build an all parameters have the default value as expected. This also works when building it via the CLI if you don't specify parameters.

          However as soon as you specify one parameter like "-p PARAM1=foo" then all the other parameters lose their default value and are blank for the build.

          I would expect that specifying one parameter should still allow others to get the default, otherwise in our scripts that invoke CLI builds, we have to put in every parameter and duplicate the default value which is error-prone and is easy to forget when changing one. Confirmed with a fresh and clean 1.370 Hudson.
          New: If you have a parameterized job with multiple parameters, all with default values, you can trigger it via an upstream build and all parameters have the default value as expected. This also works when building it via the CLI if you don't specify parameters.

          However as soon as you specify one parameter like "-p PARAM1=foo" then all the other parameters lose their default value and are blank for the build.

          I would expect that specifying one parameter should still allow others to get the default, otherwise in our scripts that invoke CLI builds, we have to put in every parameter and duplicate the default value which is error-prone and is easy to forget when changing one. Confirmed with a fresh and clean 1.370 Hudson.
          mcrooney made changes -
          Attachment New: hudson-cli-params.patch [ 19643 ]
          Danny Staple made changes -
          Component/s New: parameters [ 15594 ]
          Component/s New: ssh [ 16049 ]
          Danny Staple made changes -
          Link New: This issue is duplicated by JENKINS-11691 [ JENKINS-11691 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jason Mechler made changes -
          Labels New: lts-candidate
          vjuranek made changes -
          Labels Original: lts-candidate New: 1.480.1-fixed
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: parameters [ 15594 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 137260 ] New: JNJira + In-Review [ 187425 ]
          Łukasz Jąder made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            mcrooney mcrooney
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: