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

Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • junit-plugin
    • None

      JUnit report publication will fail if there are no unit test report XML files. I'd like to have this behaviour configurable, so that I can ignore this error.

      Cobertura reporting (for example) has a job option "Fail builds if no reports".
      In the job config.xml file for Cobertura reporting, you'll see

      <failNoReports>false</failNoReports>

          [JENKINS-22747] Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

          Paul Landolt added a comment -

          If I'm going to create a branch, should I name the branch "JENKINS-22747", or is there a protocol for such a thing from an unvetted participant?

          Paul Landolt added a comment - If I'm going to create a branch, should I name the branch " JENKINS-22747 ", or is there a protocol for such a thing from an unvetted participant?

          Oleg Nenashev added a comment -

          Hi Paul,

          If you crate a branch in your own fork, feel free to set up any name. The only recommendation is to reference the issue in the pull request title and commits.

          Oleg Nenashev added a comment - Hi Paul, If you crate a branch in your own fork, feel free to set up any name. The only recommendation is to reference the issue in the pull request title and commits.

          Paul Landolt added a comment -

          Will do. I'm just finishing some live testing with the work I've done. I should be able to check in (or push request, or whatever it's called in GIT) the changes within the next 24 hours so that it can be reviewed.

          And it does require at least 2 unit tests, so if you see the best way to test them during review, please let me know; I'd like get the chance to learn more regarding testing this particular plugin.

          Paul Landolt added a comment - Will do. I'm just finishing some live testing with the work I've done. I should be able to check in (or push request, or whatever it's called in GIT) the changes within the next 24 hours so that it can be reviewed. And it does require at least 2 unit tests, so if you see the best way to test them during review, please let me know; I'd like get the chance to learn more regarding testing this particular plugin.

          Paul Landolt added a comment - - edited

          Pull request complete.

          https://github.com/jenkinsci/junit-plugin/pull/30

          Please excuse any mistakes as I'm just learning how to work with GIT.

          Paul Landolt added a comment - - edited Pull request complete. https://github.com/jenkinsci/junit-plugin/pull/30 Please excuse any mistakes as I'm just learning how to work with GIT.

          Paul Landolt added a comment -

          Not getting a response to this so I'm going to set it "Unassigned" to see if I can get a nibble from one of the project committers.

          Paul Landolt added a comment - Not getting a response to this so I'm going to set it "Unassigned" to see if I can get a nibble from one of the project committers.

          Oleg Nenashev added a comment -

          Thanks for taking the action.
          I've totally missed your PR.I'll try to review it ASAP

          Oleg Nenashev added a comment - Thanks for taking the action. I've totally missed your PR.I'll try to review it ASAP

          Any news on the PR ? We really need a fix for this

          Xavier Gouchet added a comment - Any news on the PR ? We really need a fix for this

          Paul Landolt added a comment -

          There is a code solution for this. Oleg is reviewing the Pull request and should be accepting it into the plugin soon. (That's my take on it)

          Paul Landolt added a comment - There is a code solution for this. Oleg is reviewing the Pull request and should be accepting it into the plugin soon. (That's my take on it)

          Paul Landolt added a comment -

          Managed with Pull Request #28

          Paul Landolt added a comment - Managed with Pull Request #28

          Oleg Nenashev added a comment -

          Closing as a duplicate of JENKINS-12815 . The fchange has been released yesterday (junit-1.10)

          Oleg Nenashev added a comment - Closing as a duplicate of JENKINS-12815 . The fchange has been released yesterday (junit-1.10)

            jplandolt Paul Landolt
            landoltjp Paul Landolt
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: