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

Possibility to Exclude certain parsers from quality gates

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • warnings-ng-plugin
    • None

      While migrating from the different plugins (Task Scanner, Violations etc) happened an issue, which is a bit annoying. Currently we don't have a quality gate on open tasks but on StyleCop and warnings.

      Now that the open tasks scanner is integrated in the new warnings plugin we have some projects, which are failing just because of the open tasks.

      While I'm quite aware of the implications of haven too many todos in a project it would be nice anyway, if there were a way to exclude a parser like the open tasks from the quality gates calculation (a checkbox on each scanner would suffice) or even better, if there were a possibility to override the quality gate / health  settings on a per parser basis.

          [JENKINS-55855] Possibility to Exclude certain parsers from quality gates

          Ulli Hafner added a comment -

          This is already possible. Either use a pipeline or install the flexible publish plugin.

          Ulli Hafner added a comment - This is already possible. Either use a pipeline or install the flexible publish plugin.

            drulli Ulli Hafner
            magicmonty Martin Gondermann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: