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

option to generate clover report regardless of build status

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: cloverphp-plugin
    • Labels:
      None
    • Environment:
      Plugin version 0.3.3
      Jenkins 1.509.4 (LTS)
    • Similar Issues:

      Description

      I got a fairly large PHPUnit test suite that takes up to 40 minutes to run. Due to some weird bug in PHP or Xdebug, it ends segfaulting when PHP shutdown. Regardless, the clover.xml is properly generated and could be made a report.

      Alas, the plugin does not generate the clover report because of the build failure (added URL to console log, copied relevant part below):

      /tmp/hudson2299744543392632448.sh: line 8: 6928 Segmentation fault nice -n 19 php tests/phpunit/phpunit.php --with-phpunitdir /srv/deployment/integration/phpunit/vendor/phpunit/phpunit --exclude-group Dump,Broken,ParserFuzz,Stub --coverage-clover log/clover.xml --coverage-html /srv/org/wikimedia/integration/cover/mediawiki-core/master/php
      Build step 'Execute shell' marked build as failure
      Publishing Clover coverage report...
      No Clover report will be published due to a Build Failure
      Finished: FAILURE

      It would be very nice to have an option detecting whether the clover.xml is non empty and fresh and generate the coverage report regardless of the build status.

        Attachments

          Activity

            People

            • Assignee:
              sogabe sogabe
              Reporter:
              hashar Antoine Musso
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: