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

Health threshold rebaseline command

    XMLWordPrintable

Details

    • warnings-ng 2.2.0 (and analysis model 2.1.1)

    Description

      Health thresholds are based (delta) by comparing against some previous build.

      When, for an existing job, you add a new checker, or make an existing checker more strict, you typically cause all the health thresholds to be violated.

      In large, legacy code bases, its never realistic to expect to burn those down by any appreciable amount in any finite time.

      But, you can however, expect to attempt to contain growth of the newly identified and tracked technical debt.

      Is it possible to have some sort of UI option, command, whatever to say, "accept this build as the baseline to compare against"

      The current scenarios to effect this without the option are fairly ugly.

      Unless I'm missing something, the options as I see them are
      1. delete the job and recreate it whenever you add or make more strict a checker. This will establish the baseline at build 0 but loose all the trending and historical data
      2. raise/disable the health threshold gate (e.g from 0 new normal to 10'000 new normal), run a build so you have a new 'stable' base, then drop the limit back down.

      Attachments

        Issue Links

          Activity

            drulli Ulli Hafner added a comment -

            Is it important to choose an arbitrary build as reference or is the issue JENKINS-17196 sufficient, i.e. make the latest build the new reference?

            drulli Ulli Hafner added a comment - Is it important to choose an arbitrary build as reference or is the issue JENKINS-17196 sufficient, i.e. make the latest build the new reference?
            peteboyrocket Pete W added a comment -

            In my case setting the latest build as new reference is exactly what I want to do.

            peteboyrocket Pete W added a comment - In my case setting the latest build as new reference is exactly what I want to do.

            In a multi-branch pipeline world the reference build of feature/hotfix branches must be master/some maintenance branch.

            That would qualify as arbitrary reference build. Not having this feature makes health thresholds useless for multi-branch pipeline users because keeping the master always green would be impossible.

            cobexer Ing. Christoph Obexer added a comment - In a multi-branch pipeline world the reference build of feature/hotfix branches must be master/some maintenance branch. That would qualify as arbitrary reference build. Not having this feature makes health thresholds useless for multi-branch pipeline users because keeping the master always green would be impossible.
            drulli Ulli Hafner added a comment -

            I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page. Can you please read it carefully and comment or change it accordingly?

            drulli Ulli Hafner added a comment - I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page . Can you please read it carefully and comment or change it accordingly?

            People

              drulli Ulli Hafner
              moncreaff Greg Moncreaff
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: