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

Allow ways to configure scores of each rule set per project basis

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • ci-game-plugin
    • None
    • Platform: All, OS: All

      It would be nice to adjust the rule set so that the standard -10 (breakage), +1
      (good build), +1 (more tests) could be adjusted.

      I would think you would want to allow an overall default, and then also a
      per-project value. The rational for the per-project goes something like this.
      A project with no tests only 'breaks' if you check in something that doesn't
      compile and that should be fairly costly. A project with a large number of
      tests and that demands 100% code coverage (ala Cobertura, or similar) can be
      broken very easily simply by failing to check in tests that cover all
      code-pathways - because 'the bar' (code coverage demands) is set so high, it
      breaks much more frequently, but the penalty for breaking such a build should
      not be as much. One size doesn't fit all.

            redsolo redsolo
            jbennett2091 jbennett2091
            Votes:
            7 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: