[
https://issues.jenkins-ci.org/browse/JENKINS-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162630#comment-162630
]
SCM/JIRA link daemon commented on JENKINS-8916:
-----------------------------------------------
Code changed in jenkins
User: Fred G
Path:
src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/config.jelly
src/main/resources/hudson/plugins/parameterizedtrigger/BuildTriggerConfig/config.jelly
http://jenkins-ci.org/commit/parameterized-trigger-plugin/3f6097a82679a76d8b0b03498d9c9a392b77f6fc
Log:
[FIXED JENKINS-8916] Allowing same type of parameter for triggered build
more than once seems redundant
It requires Jenkins core version 1.463 to work, but it's fully
backwards compatible.
> Allowing same type of parameter for triggered build more than once seems
> redundant
> ----------------------------------------------------------------------------------
>
> Key: JENKINS-8916
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8916
> Project: Jenkins
> Issue Type: Bug
> Components: parameterized-trigger
> Affects Versions: current
> Reporter: Fred G
> Assignee: Fred G
> Priority: Minor
>
> While working on [JENKINS-7377] I noticed that it's redundant and confusing
> to allow the same type of parameter for a triggered build more than once.
> For example, right now it's possible to specify "Current Build Parameters",
> or "Subversion Revision" two or more times.
> The only type where it might make sense is "Parameters from properties file".
> I think for every type of parameters a simple checkbox is sufficient.
> I'll try to make the necessary changes and open a pull request, but
> appreciate comments or criticism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
