[
https://issues.jenkins-ci.org/browse/JENKINS-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158565#comment-158565
]
Chris Graham commented on JENKINS-2068:
---------------------------------------
The point of this issue, was that calling the same job, the same way (eg: mvn
clean package site) produced *DIFFERENT* results displayed in Hudson.
The differences were observed then the same project, called the same way, was
called either via a 'Free Style' or 'Maven2' job type.
So, @jieryn, is it not a bad or improper usage of maven, as the same goals are
being executed for both job types.
So it is either a bug in the way that the reports are processed, or the way in
that the Maven2 jobs are executed within hudson, given the same execution
criteria.
I would hope that calling 'mvn clean package site' would be executed the same
way, irrespective of the job type.
> Junit test showing twice
> ------------------------
>
> Key: JENKINS-2068
> URL: https://issues.jenkins-ci.org/browse/JENKINS-2068
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: Chris Graham
> Attachments: hudson-junit.zip
>
>
> Using the Maven job type, if the surefire results are run twice (eg clean
> package site) the test results are counted twice.
> If we use the same pom for a freestyle project, the results are shown
> correctly.
--
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
