Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14585

Test Failure Claim Link not present for Maven test results

      First, thanks for this great plugin.

      This seems to work great for Freestyle projects.

      We're seeing an issue, however, when using it with Maven projects.

      In particular, although it is possible to claim build failures, it does not seem to be possible to claim test failures in the maven results – the 'claim' link is not present, nor is the text saying this test has not yet been claimed, even though we have enabled the 'allow claiming of failed tests' in our job configuration.

          [JENKINS-14585] Test Failure Claim Link not present for Maven test results

          Steve Roth created issue -

          Steve Roth added a comment -

          forgot to mention; this is on Jenkins 1.473

          Steve Roth added a comment - forgot to mention; this is on Jenkins 1.473

          kutzi added a comment - - edited

          Seems like have to configure this differently for Maven builds: Post build actions -> Additional test report features
          Did you do that?

          kutzi added a comment - - edited Seems like have to configure this differently for Maven builds: Post build actions -> Additional test report features Did you do that?
          Christian Bremer made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Christian Bremer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

          kutzi added a comment -

          Actually, I was able to reproduce it on my instance (or I wasn't able to find the claim button for the tests)
          Christian where do you see the button?

          kutzi added a comment - Actually, I was able to reproduce it on my instance (or I wasn't able to find the claim button for the tests) Christian where do you see the button?
          kutzi made changes -
          Assignee New: Christian Bremer [ ki82 ]
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

          My bad, I closed this as part cleaning up some old issues.
          (Since you commented on this more than 2 weeks ago implying that it was a configuration error and without a reply from Steve Roth.)

          Christian Bremer added a comment - My bad, I closed this as part cleaning up some old issues. (Since you commented on this more than 2 weeks ago implying that it was a configuration error and without a reply from Steve Roth.)

          kutzi added a comment - - edited

          Probably that this doesn't work because the plugin only implements 'TestDataPublisher', but not 'MavenTestDataPublisher'
          Though, I wonder why it shows up as an option in the Maven job config, at all.

          No sorry, that's completely wrong MavenTestDataPublisher is a Recorder for Maven jobs which applies the TestDataPublishers to Maven jobs.
          So this 'should' work

          kutzi added a comment - - edited Probably that this doesn't work because the plugin only implements 'TestDataPublisher', but not 'MavenTestDataPublisher' Though, I wonder why it shows up as an option in the Maven job config, at all. No sorry, that's completely wrong MavenTestDataPublisher is a Recorder for Maven jobs which applies the TestDataPublishers to Maven jobs. So this 'should' work

          kutzi added a comment -

          I've just debugged this and it seems like this is a bug in the MavenTestDataPublisher in Jenkins core.
          MavenTestDataPublisher is only called for the aggregated MavenModuleSetBuild (and not for the individual MavenBuilds) - which may be okay or not, that's debatable.
          However, the bug is that it checks if there is a SurefireReport action attached to the MavenModuleSetBuild, but there is never is one:
          MavenModuleSetBuilds only have SurefireAggregatedReports!

          kutzi added a comment - I've just debugged this and it seems like this is a bug in the MavenTestDataPublisher in Jenkins core. MavenTestDataPublisher is only called for the aggregated MavenModuleSetBuild (and not for the individual MavenBuilds) - which may be okay or not, that's debatable. However, the bug is that it checks if there is a SurefireReport action attached to the MavenModuleSetBuild, but there is never is one: MavenModuleSetBuilds only have SurefireAggregatedReports!

            ki82 Christian Bremer
            sroth Steve Roth
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: