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

            moncreaff Greg Moncreaff created issue -
            drulli Ulli Hafner made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-17196 [ JENKINS-17196 ]
            drulli Ulli Hafner made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Resolved [ 5 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 154628 ] JNJira + In-Review [ 194970 ]
            cobexer Ing. Christoph Obexer made changes -
            Resolution Duplicate [ 3 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            drulli Ulli Hafner made changes -
            Status Reopened [ 4 ] Open [ 1 ]
            drulli Ulli Hafner made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 17282 ]
            drulli Ulli Hafner made changes -
            Component/s warnings-ng-plugin [ 24526 ]
            Component/s warnings-plugin [ 15513 ]
            drulli Ulli Hafner made changes -
            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.
            jjHealth 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.
            drulli Ulli Hafner made changes -
            Rank Ranked higher
            drulli Ulli Hafner made changes -
            Description jjHealth 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.
            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.
            drulli Ulli Hafner made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            drulli Ulli Hafner made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Fixed but Unreleased [ 10203 ]
            drulli Ulli Hafner made changes -
            Released As warnings-ng 2.2.0 (and analysis model 2.1.1)
            Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: