Build success and failure count should be monotonically increasing number

Steps to reproduce

How can we reproduce the issue

1. Create a test job which runs regularly at least 10 times a day.
2. It should fail 30% of the time to build collect failure count
3. Check the failure and success count for the test job for a period of one week

Expected behaviour

The count for success and failure should never decrease

Actual behaviour

The count for success and failure drops for a couple of days in the week time period

Server configuration

Operating system: Centos 7

Jenkins Version: 2.222.1

Plugin Version: 2.0.7 and 2.0.6 (tried on both)

Notify

@markyjackson-taulia

[judos]

Hello @markyjackson-taulia , please reopen this ticket. Steps to reproduce:

• Set jenkins to throw away old builds. E.g. only keep 30 builds. (similar to screenshot below)
• make sure you already have 30 builds
• trigger another build
• metric counter stays still at 30 builds (this counter is really not working as it should)
• Now let’s increase jenkins configuration to keep the oldest 32 builds (see screenshot)
• Trigger build
• Counter now increases to 31 (but will not go past 32!) Let’s now decrease the counter for fun:
• Delete a build in jenkins
• Counter goes down by 1

The metric probably just uses the number of builds jenkins has stored. But the counter must be individually tracked such that it does not stall when there is a build limit set. (or also when builds are removed manually)

Workaround:

1. Remove the build limit in jenkins for the moment, this however causes jenkins to store excessive amount of information which is probably undesirable…
2. For monitoring I now just the use the “default_jenkins_builds_health_score” which is probably enough if you want an alarm.

[markyjackson-taulia]

Because I cannot reproduce this and the issue went stale.