Conversation
|
@marcosteffan : I didn't try this but I hope it should fix JENKINS-52854 issue ! |
It seems that the configuration name has changed and this break the
compatibility:
Before (v1.22 or before):
<org.jenkinsci.plugins.cppcheck.CppcheckPublisher>
<cppcheckConfig>
<pattern>**/cppcheck.xml</pattern>
After (v1.23):
<org.jenkinsci.plugins.cppcheck.CppcheckPublisher plugin="cppcheck@1.23">
<config> <!-- Not cppcheckConfig anymore -->
<pattern>**/cppcheck.xml</pattern>
You can check the generated config.xml file by looking at this address:
https://<JENKINS_URL>/job/<JOBNAME>/config.xml
I am not sure how the XML scheme is generated but I guess it inspects
the name of the variables. Then this change should fix the
compatibility issue.
Issue: JENKINS-52854
Fixes: 32710c4 (Fixed storing plugin-settings)
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
I mentioned it on the Jenkins ticket but I forgot to mention it here as well. I did test it and it does fix the Jenkins issue ;-) |
|
the change in 32710c4 also broke all projects made by https://docs.openstack.org/infra/jenkins-job-builder/ so merging would fix issues there |
|
@eckschi Yes, I confirm that. Note that you can temporary use the .hpi from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fcppcheck-plugin/detail/PR-44/2/artifacts/ |
|
@marcosteffan |
|
Hi, Best regards |
|
@marcosteffan : thx you for the fix. I guess we can abandon this one |
It seems that the configuration name has changed and this break the
compatibility:
Before (v1.22 or before):
After (v1.23):
You can check the generated config.xml file by looking at this address:
I am not sure how the XML scheme is generated but I guess it inspects
the name of the variables. Then this change should fix the
compatibility issue.
Linked to this issue: JENKINS-52854
Signed-off-by: Matthieu Baerts matthieu.baerts@tessares.net