|
||||||||
|
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/d/optout.
The problem is that this actually is a rather specialized use case not a lot of users will face. (And the few interested in this will have a slightly different problem, like wanting to translate the numbers 1-6 to percentages 16, 33, 50, 67, 83, 100).) Adding support for it in core will result in additional clutter for almost everyone while helping very few. There's numerous parameter-related plugins already that can probably do this for you, not to mention env-inject rewriting build parameters in a script.
Me saying "This should be done in a plugin" does not mean "This should not be done at all". It just means it makes no sense to add it to Jenkins core.