|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
one additional note about the maven project:
If the job is a maven project and you use such text parameter, also all pre- and post steps will fail (if they invoke for example a maven or ant tool). In such case you can "unset" the parameter with the env-inject plugin and remember it into another variable ... this variable will then not added as a parameter to the job ... but this is still very hackish.
So the problem exists also for maven jobs with pre- or post-steps.
I do not know, if it is a good idea to reduce the priority, because of the possibility to "destroy" the Jenkins slave with a unchecked parameter ... but I do not know enough about the JIRA rules for this project.
Possible more investigation about the consequences should be made, to decide about the priority.