Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JENKINS-16475 Build stats graph configuration lost after Jenkins Restart #13

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

rafal-prasal
Copy link

GlobalBuildStats configuration was removed

Root Cause:
\1 if there were issue with Jobresult xml file then major configuration file was destroyed
\2 after second run it was overwritten

Changes I made
\1 Save will not happen before Load
\2 Load is mutually exlusive with Save
\3 Saves are in separate threads there is only one allowed at a time and others will wait
\4 If there is an issue with Jobresult xml file then it will be ignored and renamed to .error-timestamp
\5 if there is an issue with major configuration then file will be renamed to .bak-timestamp so in the second run it won’t get overwritten

@rafal-prasal rafal-prasal changed the title Fix for configuration removal JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Apr 16, 2018
@grazius
Copy link

grazius commented Jul 24, 2019

Hello
anyone can integrate PR on this plugin ?
or this plugin is dead ?

@sanadhis
Copy link

Hello is this PR still relevant?
I guess so since my global stats graphs gone after one restart?

My setup:
Jenkins: 2.479.2
global-build-stats: 316.vf8870f424d78

@MarkEWaite
Copy link
Contributor

MarkEWaite commented Feb 19, 2025

Hello is this PR still relevant? I guess so since my global stats graphs gone after one restart?

The PR may still be relevant, but it has merge conflicts that need to be resolved. If you are interested in the changes proposed in this pull request, you can take those changes and prepare a new pull request that resolves the conflicts. That would allow you to test the changes and confirm that they resolve the issue that you are seeing.

You may also want to look at the other pull requests in this repository, since they may also be related. In particular:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants