Daniel Beck commented on Bug JENKINS-26770

Although the 404 indicates file is not there, could that mean the burn in plugin hasn't run and generated a change report?

BurnIn is a job name (and view name). The plugin is JobConfigHistory. Not sure what the cause could be. Should probably be another bug report to investigate further.

I'm able to reproduce the problem on 1.598. The screen shot I've attached is from v1.598.

Yeah I hedged that a bit with the recommendation to ensure current Jenkins. I'd be happy to take a look at a bug report about that. Please make sure to follow the instructions on the linked wiki page, even if it's a disgustingly long read. Thanks!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to