![]() |
|
|
|
|
Change By:
|
centic
(01/Mar/13 3:30 PM)
|
|
Summary:
|
Parameters with newlines
are not applied correctly when triggering a rebuild
should be stored as TextParameterValue
|
|
Description:
|
For one of my Jobs I need multiple lines of text in one parameter, e.g.
In the parameterized build trigger plugin I specify this parameter with "\n":
{quote}
PROJECTPROPERTIES=sonar.projectKey=preismonitor-lokal\nsonar.projectName=preismonitor-lokal
{quote}
This
The "\n"
correctly passes the parameter with newline characters to
the second build
an upcoming biuld
.
In the build.xml of the jenkins-build, the newlines are stored normally
, however there are problems later on if other plugins work with this data because the parameter-type is "StringParameterValue" instead of "TextParameterValue":
{code:xml}<hudson.model.StringParameterValue>
<name>PROJECTPROPERTIES</name>
<value>sonar.projectKey=preismonitor-lokal
sonar.projectName=preismonitor-lokal</value>
</hudson.model.StringParameterValue>{code}
However
E.g.
if I use the rebuild-plugin to re-trigger the build later on, it seems to cut off the newlines and pass the string in one single line, which causes the rebuild to fail:
{quote}
... -Dsonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal ...
{quote}
I will attach a patch which creates a TextParameterValue if the value contains newlines. This makes this work in all cases.
|
|
Component/s:
|
parameterized-trigger
|
|
Component/s:
|
rebuild
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
