|
Recognize test results from eviware:maven-soapui-plugin
------------------------------------------------------- Key: JENKINS-11353 URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 Project: Jenkins Issue Type: Improvement Components: maven2, plugin Affects Versions: current Reporter: Nathan McDonald Priority: Minor maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). If using maven project, these tests do not show up. There's good info here about setting maven,soapui tests and jenkins up http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan McDonald updated JENKINS-11353: -------------------------------------- Attachment: SurefireArchiver.java.diff My attempt at adding this to SurefireArchiver.java patched against tagged version 1.434 > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan McDonald updated JENKINS-11353: -------------------------------------- Attachment: SurefireArchiver.java.diff Sorry, just realised i did that last diff in the wrong direction. this is correct > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153914#comment-153914 ] Nathan McDonald commented on JENKINS-11353: ------------------------------------------- the soapui plugin config we are using is below: {code:xml} <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-plugin</artifactId> <version>3.6.1</version> <executions> <execution> <id>start-soapui-mocks</id> <phase>pre-integration-test</phase> <goals> <goal>mock</goal> </goals> <configuration> <noBlock>true</noBlock> </configuration> </execution> <execution> <id>run-soapui-tests</id> <phase>integration-test</phase> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <projectFile>${basedir}/test/soap-ui/${artifactId}-soapui-project.xml</projectFile> <outputFolder>${basedir}/target/surefire-reports</outputFolder> <junitReport>true</junitReport> <exportAll>true</exportAll> <printReport>true</printReport> <testFailIgnore>true</testFailIgnore> </configuration> </plugin> {code} > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157838#comment-157838 ] Ryan Murfitt commented on JENKINS-11353: ---------------------------------------- Pull request https://github.com/jenkinsci/jenkins/pull/352 > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157891#comment-157891 ] Aidan Foley commented on JENKINS-11353: --------------------------------------- It looks like this commit just has support for the maven-soapui-plugin. Would you be able to add support for the maven-soapui-pro plugin as well please? > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157891#comment-157891 ] Aidan Foley edited comment on JENKINS-11353 at 1/18/12 5:38 PM: ---------------------------------------------------------------- It looks like this commit just has support for the maven-soapui-plugin. Would you be able to add support for the maven-soapui-pro-plugin as well please? was (Author: foley): It looks like this commit just has support for the maven-soapui-plugin. Would you be able to add support for the maven-soapui-pro plugin as well please? > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157906#comment-157906 ] Ryan Murfitt commented on JENKINS-11353: ---------------------------------------- Added maven-soapui-pro-plugin support > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158394#comment-158394 ] SCM/JIRA link daemon commented on JENKINS-11353: ------------------------------------------------ Code changed in jenkins User: Olivier Lamy Path: maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java http://jenkins-ci.org/commit/jenkins/bc3766f41f379fe517d0a4931690698e3110dfdf Log: Merge pull request #352 from puug/master Fix for JENKINS-11353 thanks. > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158395#comment-158395 ] SCM/JIRA link daemon commented on JENKINS-11353: ------------------------------------------------ Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/1bdedc2ade1ca55f77026d14d22cc2c5f635b57b Log: add changelog entry for [JENKINS-11353] > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158398#comment-158398 ] dogfood commented on JENKINS-11353: ----------------------------------- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1508|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1508/] [FIXED JENKINS-11353] (Revision 35c48cfcf563ad4429b51f7c920ee34159d8b4e9) add changelog entry for [JENKINS-11353] (Revision 1bdedc2ade1ca55f77026d14d22cc2c5f635b57b) Result = SUCCESS rmurfitt : [35c48cfcf563ad4429b51f7c920ee34159d8b4e9|https://github.com/jenkinsci/jenkins/commit/35c48cfcf563ad4429b51f7c920ee34159d8b4e9] Files : * maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java Olivier Lamy : [1bdedc2ade1ca55f77026d14d22cc2c5f635b57b|https://github.com/jenkinsci/jenkins/commit/1bdedc2ade1ca55f77026d14d22cc2c5f635b57b] Files : * changelog.html > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163126#comment-163126 ] Roland Asmann commented on JENKINS-11353: ----------------------------------------- Has this been released yet? > Recognize test results from eviware:maven-soapui-plugin > ------------------------------------------------------- > > Key: JENKINS-11353 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11353 > Project: Jenkins > Issue Type: Improvement > Components: maven2, plugin > Affects Versions: current > Reporter: Nathan McDonald > Priority: Minor > Attachments: SurefireArchiver.java.diff, SurefireArchiver.java.diff > > > maven-soap-ui plugin is capable of outputting surefire/junit style reports: http://www.soapui.org/Test-Automation/maven-2x.html > If using freestyle project in jenkins, can specify to look in report output directory and jenkins will register the tests (test results on project show them). > If using maven project, these tests do not show up. > There's good info here about setting maven,soapui tests and jenkins up > http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22420 > In comments at the bottom, you can see that jenkins will not recognize tests by default. Workaround is to use a freestyle project, but then we lose ability to have things like the 'perform maven release' button on the job. > Have investigated this, seems to be an issue with hudson.maven.reporters.SurefireArchiver needing to have every plugin registered that it will consider test reports from. Since it's hardcoded into the file, guess the simplest way to fix this is to patch it to include the soapui plugin. > Seems similar to this request for failsafe plugin: https://issues.jenkins-ci.org/browse/JENKINS-4229 -- 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
| Powered by Nabble | Edit this page |

Code changed in jenkins
User: puug
Path:
maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java
http://jenkins-ci.org/commit/jenkins/35c48cfcf563ad4429b51f7c920ee34159d8b4e9
Log:
[FIXED JENKINS-11353]
Now recognises test results created by the maven-soap-ui plugin