We use the jenkins-maven-plugin (http://evgeny-goldin.com/wiki/Jenkins-maven-plugin) to generate our jobs due to the big amount of similar jobs we have.

The plugin generates the config.xml files into the JENKINS_HOME/jobs sub-folders and we do a full restart after the generation.

On some jobs jenkins seems to get confused about the build history. While navigation between builds via the UI works flawlessly there are other effects showing up:

• Dashboard/View loading takes a long time (see stacktrace dashboard.txt)
• Rendering of test trend chart fails (see trendchart.txt for stacktrace)
• Builds fail when generating/publishing test results (error: "Invalid XML Attributes" no stacktrace available atm, but it was a similiar one with #getPreviousBuild in it.)

This does not affect all builds whose jobs are generated using the plugin. Most of them work just fine.

The jobs that have those issues have the build history available and their history is shown on the jobs overview page. All builds can be navigated to using the ui.

I am not sure if this bug is related to jenkins or the generating maven plugin, but from my understanding, jenkins should not show those effects after the replacing of config.xml files.