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

A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

    XMLWordPrintable

Details

    Description

      A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".

      Now the request body like :

      {"id":"2", "parameters":[]}

      it works well, but the field "parameters" is not used.

      I guess If we remove "parameters" like {"id":"2"}, The function can also work well.
      Perhaps support both different struct is a better choice.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          zhuxiaoyang zhu xiaoyang created issue -
          zhuxiaoyang zhu xiaoyang made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          zhuxiaoyang zhu xiaoyang made changes -
          Description A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check proceed, but it will be returned an error: "parameters is required"

          Now the request body like :

          {"id":"2", "parameters":[]}

          it works well, but the field "parameters" is not used.

          I guess remove "parameters" like \{"id":"2"} is more restful.           		A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required"

          Now the request body like :

          {"id":"2", "parameters":[]}

          it works well, but the field "parameters" is not used.

          I guess remove "parameters" like \{"id":"2"} is more restful.
          zhuxiaoyang zhu xiaoyang made changes -
          Description A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required"

          Now the request body like :

          {"id":"2", "parameters":[]}

          it works well, but the field "parameters" is not used.

          I guess remove "parameters" like \{"id":"2"} is more restful.           		A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".

          Now the request body like :

          {"id":"2", "parameters":[]}

          it works well, but the field "parameters" is not used.

          I guess remove "parameters" like \{"id":"2"} is more restful.
          zhuxiaoyang zhu xiaoyang made changes -
          Description A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".

          Now the request body like :

          {"id":"2", "parameters":[]}

          it works well, but the field "parameters" is not used.

          I guess remove "parameters" like \{"id":"2"} is more restful.           		A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".

          Now the request body like :

          {"id":"2", "parameters":[]}
          it works well, but the field "parameters" is not used.

          I guess If we remove "parameters" like \{"id":"2"}, The function can also work well.
          Perhaps support both different struct is a better choice.

          People

            zhuxiaoyang zhu xiaoyang
            zhuxiaoyang zhu xiaoyang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: