-
Bug
-
Resolution: Fixed
-
Blocker
After adding Publish Performance Test Report and saved the job configuration, unable to save changes further to the Job. Click on Save does not shows any response. Click on Apply just shows blank pop up with no information.
Before adding that plug-in user is able to make changes and save the job configuration.
Jenkins Version: 2.281
Performance Plugin 3.18
Performance Publisher plugin 8.09
- is duplicated by
-
-
- Resolved
-
[JENKINS-64990] Unable to save job configuration changes once saved with Publish Performance Result
Nico Po
added a comment - Same issue.
Is there any workaround? 
Gabor V
added a comment - Sure, a really nice one: you have to deploy a Jenkins v2.263 somewhere else and set up the perf plugin there then push the results and run the post build action there.
(Since v2.263 we are suffering with different job configuration issues. Planning to move to some other CI solution.)
Gabor V
added a comment - Sure, a really nice one: you have to deploy a Jenkins v2.263 somewhere else and set up the perf plugin there then push the results and run the post build action there.
(Since v2.263 we are suffering with different job configuration issues. Planning to move to some other CI solution.)
Sasitharan
added a comment - As unable to remove performance plugin from UI we need to remove the plugin part form the respective xml of the job. After removing the plugin Jenkins works as expected and able to make required changes. That is the only workaround that too to proceed with making changes apart from Performance result. Adding performance report once again makes the job to stuck up again.
Sasitharan
added a comment - As unable to remove performance plugin from UI we need to remove the plugin part form the respective xml of the job. After removing the plugin Jenkins works as expected and able to make required changes. That is the only workaround that too to proceed with making changes apart from Performance result. Adding performance report once again makes the job to stuck up again. 
Tyler
added a comment - niqo I think using a pipeline job instead of Freestyle could be a reasonable workaround. I've done some limited testing and haven't run into any issues (yet) in using this plugin with Pipelines.
Tyler
added a comment - niqo I think using a pipeline job instead of Freestyle could be a reasonable workaround. I've done some limited testing and haven't run into any issues (yet) in using this plugin with Pipelines. Nico Po
added a comment - This blocking issue exist since more than 2 months, should we consider this plugin deprecated? This plugin was great, but now it's not usable anymore...
Nico Po
added a comment - This blocking issue exist since more than 2 months, should we consider this plugin deprecated? This plugin was great, but now it's not usable anymore... niqo the last release of the plugin was 3 months ago. That's quite recent.
I'm sure the plugin maintainers would be willing to consider a pull request that resolves the issue. There are relatively few references to HTML tables in the plugin source code. Please feel free to submit a pull request to resolve the issue.
Thomas de Grenier de Latour
added a comment - Here is my attempt at fixing this: PR-200 Nico Po
added a comment - Thank you so much Thomas de Grenier de Latour ! 
Artem Fedorov
added a comment - Released in 3.20 
For us it looks like this: