|
||||||||
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 |
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... werni...@java.net (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... xiaopan3...@gmail.com (JIRA)
- [JIRA] (JENKINS-15501) Can't do "Rebuild... cjo9...@java.net (JIRA)
I think to make this rebuild action a bit more extend-able it should expose a interface than can be implemented in other parameter plugins. This would then allow code reuse of the original process for the parameter and always have the same implementation.
This would mean that the rebuild plugin does not have to know about all the different parameter types.