Henning Groß created JENKINS-12996:
--------------------------------------
Summary: accept test results from different plugins
Key: JENKINS-12996
URL: https://issues.jenkins-ci.org/browse/JENKINS-12996
Project: Jenkins
Issue Type: Patch
Components: core
Reporter: Henning Groß
Attachments: adds_mvn-remote-test_plugin.patch,
refactoring_of_SurefireArchiver1.patch
We have developed this plugin: http://evolvis.org/projects/mvn-remote-test/ and
we need the fetched test results to be included in jenkins build. Based on the
old code i have attached a patch that simply adds our plugin in the old manner.
This patch is called "adds_mvn-remote-test_plugin.patch".
As I do not think the code was/is smart that way, i have attached a second
patch called "refactoring_of_SurefireArchiver1.patch". It has another approach.
If a plugin is not know but specifies a reportDirectory it will still get
recognized. This enables people to write plugins that do NOT have to be named
explicitly. For backwars compatibility I have retained the old behaviour and
kept the hard-coded plugins. As I am having problems building the trunk and
running the tests and also dont have the time to test it fully on our ci I have
to ask you to review the patch properly before accepting it. I am also not
perfectly sure if I have though every case through but it pretty much should
work ;)
Maybe you can accept "adds_mvn-remote-test_plugin.patch" immediately to enable
us to complete our plugin and if you like
"refactoring_of_SurefireArchiver1.patch" is my contribution to jenkins code
base which you can accept/mopdify/use later.
Thanks a lot and keep up the good work!
--
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
