• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: build-failure-analyzer-plugin
• Labels:

  None
• Environment:

  Jenkins v. 2.194, BFA v. 1.23.0
  
  Noticed this behaviour on our production server then replicated it in a fresh Jenkins/Build Failure Analyzer install in a docker container.

1. 

   Screen Shot 2019-09-30 at 15.39.42.png

   19 kB

   2019-09-30 20:57

[JENKINS-59593] enableStatistics and successfulLogging config values are not loaded properly

Stephen Humphries created issue - 2019-09-30 20:59

Stephen Humphries made changes - 2019-10-01 13:28

Description

Original: (This applies when MongoDB is selected as the KB type.) The Build Failure Analyzer settings on the Manage Jenkins > Configure System page are always loaded with "Enable statistics logging" selected and "Enable statistics logging of successful builds" unselected, regardless of the values that were previously set and persisted to build-failure-analyzer.xml. Anytime the configuration page is saved, then, these two options are reset, even if the user did not touch them. The result is that anytime changes are made to the configuration, care must be taken to ensure that the statistics checkboxes are set as desired – since so many settings are included in this single page, this is not particularly safe and can result in important information being lost.

New: (This applies when MongoDB is selected as the KB type.) The Build Failure Analyzer settings on the Manage Jenkins > Configure System page are always loaded with "Enable statistics logging" selected and "Enable statistics logging of successful builds" unselected, regardless of the values that were previously set and persisted to build-failure-analyzer.xml. Anytime the configuration page is saved, then, these two options are reset, even if the user did not touch them. The result is that any time changes are made to the configuration, care must be taken to ensure that the statistics checkboxes are set as desired – since so many settings are included in this single page, this is not particularly safe and can result in important information being lost.

Tomas Westling made changes - 2019-10-02 11:38

Link

New: This issue is duplicated by JENKINS-59610 [ JENKINS-59610 ]

Tomas Westling made changes - 2019-10-04 08:31

Link

Original: This issue is duplicated by JENKINS-59610 [ JENKINS-59610 ]

Tomas Westling made changes - 2019-10-04 08:31

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Tomas Westling made changes - 2019-10-04 12:18

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Tomas Westling made changes - 2019-10-16 10:42

Link

New: This issue relates to JENKINS-59610 [ JENKINS-59610 ]

Tomas Westling made changes - 2019-10-16 10:43

Released As		New: 1.23.1
Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Closed [ 6 ]