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

Option to not mark a build as failure when the Cucumber report is missing

      Some of our job executions don't fail but skip all testing (duplicated builds), we mark these executions as passed automatically but this plugin marks them as fail because the report is not present.
      I want to keep this plugin enabled but I don't like the plugin marking the builds as failed when I previously set them to successful.

          [JENKINS-31027] Option to not mark a build as failure when the Cucumber report is missing

          James Nord added a comment -

          probable workaround is to probably create an empty json file.

          James Nord added a comment - probable workaround is to probably create an empty json file.

          My current workaround is to wrap the cucumber-test-results-plugin step into another conditional step (https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin), if the build skips testing because it's not necessary, then this plugin is not executed.
          The bad part of these workaround solutions is that they introduce more logic and complicate our Jenkins jobs.

          Sebastian Lobato Genco added a comment - My current workaround is to wrap the cucumber-test-results-plugin step into another conditional step ( https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin ), if the build skips testing because it's not necessary, then this plugin is not executed. The bad part of these workaround solutions is that they introduce more logic and complicate our Jenkins jobs.

            Unassigned Unassigned
            neoranga Sebastian Lobato Genco
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: