[
https://issues.jenkins-ci.org/browse/JENKINS-13188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160791#comment-160791
]
Will Cain edited comment on JENKINS-13188 at 3/26/12 6:46 PM:
--------------------------------------------------------------
Here's a work-around I discovered while attempting to make the SurefireArchiver
change. Turns out Jenkins will already notice jasmine-maven-plugin results
when run through surefire-maven-plugin. You just have to tell
surefire-maven-plugin explicitly to run test goal, preferably during package
phase.
For example:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.12</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
<!-- ensures surefire runs after jasmine: -->
<phase>package</phase>
</execution>
</executions>
</plugin>
{code}
My testing demonstrate this indeed works. For me this greatly reduces the need
for a Jenkins change.
was (Author: willcainsvg):
Here's a work-around I discovered while attempting to make the
SurefireArchiver change. Turns out Jenkins will already notice
jasmine-maven-plugin results when run through surefire-maven-plugin. You just
have to tell surefire-maven-plugin explicitly to run test goal, preferably
during package phase.
For example:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.12</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
<!-- ensures surefire runs after jasmine: -->
<phase>package</phase>
</execution>
</executions>
</plugin>
My testing demonstrate this indeed works. For me this greatly reduces the need
for a Jenkins change.
> Recognize test results from com.github.searls:jasmine-maven-plugin
> ------------------------------------------------------------------
>
> Key: JENKINS-13188
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13188
> Project: Jenkins
> Issue Type: Improvement
> Components: maven2, plugin
> Affects Versions: current
> Reporter: Will Cain
> Priority: Minor
> Labels: maven2, plugin
>
> jasmine-maven-plugin plugin is capable of outputting surefire/junit style
> reports: http://searls.github.com/jasmine-maven-plugin/
> While Jenkins will recognize jasmine-maven-plugin test results in a
> free-style(/freestyle) project, in a Maven project the results do not show.
> Free-style is nice, but then full Maven project functionality is not
> available, such as release and other goals.
> See jasmine-maven-plugin author searls comment here, quoted below:
> https://github.com/searls/jasmine-maven-plugin/issues/9
> "JUnit XML reports can only be specified by the user on freestyle projects.
> To get a maven2 project to see Jasmine's XML reports, SurefireArchiver would
> need to be updated to include the jasmine-maven-plugin's GAV."
> This issue is similar to JENKINS-11353. I expect it could be resolved, as
> searls suggests, in a similar manner. Looks like
> hudson.maven.reporters.SurefireArchiver would need to include registration
> for jasmine-maven-plugin.
--
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
