Quality Gates for new model code coverage plugin

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      The code coverage plugin currently sets the results of a build to stable, unstable or failed based on an evaluation of the old model in CoverageProcessor#processThresholds.

      A similar functionality is required for the new model in CoverageNode: this new functionality should create a QualityGateStatus (similar to the warnings plugin) based on a list of QualityGates for a specific CoverageNode (or for the aggregated coverage metric results of the CoverageNode). The evaluation should be logged into a simple logger instance like in QualityGateEvaluator#FormattedLogger.
      A similar functionality is available in the warnings plugin: it sets the quality gate result based on an evaluation of the number of warnings:

      A quality gate has three properties:

      • the percentage that must be achieved in order to pass the quality gate
      • the type of coverage that will be evaluated (Class, Line, Branch, etc.)
      • the build status that should be used if the quality gate is not passed (failed or unstable)

            Assignee:
            Ulli Hafner
            Reporter:
            Ulli Hafner
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: