• Type: New Feature
• Resolution: Done
• Priority: Minor
• Component/s: parameterized-remote-trigger-plugin
• Labels:

  None
• Environment:

  Jenkins: 2.332.3
  OS: Linux - 5.4.188-104.359.amzn2.x86_64
  ---
  Parameterized-Remote-Trigger:3.1.5.1
  

[JENKINS-68737] Support multi-line parameters in parameterized remote trigger plugin

Cyprien Quilici created issue - 2022-06-10 08:24

Cyprien Quilici made changes - 2022-06-10 08:24

Description

Original: Currently, the parameters are passed as a big multi-line string that is parsed by the plugin line-by-line. This has a consequence: passing multi-line parameters for the remote Jenkins instance does not work, only the first line ends up in the parameter I fiddled with the code and opened a [https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/79|pull request] with a suggestion for a fix.   You can find a more detailed description of the problem there too. Note: While fixing the parsing, I also happened to stumble on another [https://issues.jenkins.io/browse/JENKINS-58818|bug] linked to it that I fixed in my PR too.

New: Currently, the parameters are passed as a big multi-line string that is parsed by the plugin line-by-line. This has a consequence: passing multi-line parameters for the remote Jenkins instance does not work, only the first line ends up in the parameter I fiddled with the code and opened a [pull request|https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/79] with a suggestion for a fix.   You can find a more detailed description of the problem there too. Note: While fixing the parsing, I also happened to stumble on another [https://issues.jenkins.io/browse/JENKINS-58818|bug] linked to it that I fixed in my PR too.

Cyprien Quilici made changes - 2022-06-10 08:25

Description

Original: Currently, the parameters are passed as a big multi-line string that is parsed by the plugin line-by-line. This has a consequence: passing multi-line parameters for the remote Jenkins instance does not work, only the first line ends up in the parameter I fiddled with the code and opened a [pull request|https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/79] with a suggestion for a fix.   You can find a more detailed description of the problem there too. Note: While fixing the parsing, I also happened to stumble on another [https://issues.jenkins.io/browse/JENKINS-58818|bug] linked to it that I fixed in my PR too.

New: Currently, the parameters are passed as a big multi-line string that is parsed by the plugin line-by-line. This has a consequence: passing multi-line parameters for the remote Jenkins instance does not work, only the first line ends up in the parameter I fiddled with the code and opened a [pull request|https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/79] with a suggestion for a fix.   You can find a more detailed description of the problem there too. Note: While fixing the parsing, I also happened to stumble on [another bug|https://issues.jenkins.io/browse/JENKINS-58818] linked to it that I fixed in my PR too.

KaiHsiang Chang made changes - 2022-06-11 16:54

Resolution		New: Done [ 10000 ]
Status	Original: Open [ 1 ]	New: Fixed but Unreleased [ 10203 ]

KaiHsiang Chang made changes - 2022-06-11 17:19

Released As		New: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.1.6
Status	Original: Fixed but Unreleased [ 10203 ]	New: Resolved [ 5 ]

KaiHsiang Chang made changes - 2022-06-13 16:22

Released As

Original: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.1.6

New: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.1.6.1