Jenkins 35096 altran cppcheck plugin pipeline support#37
Jenkins 35096 altran cppcheck plugin pipeline support#37AltranManatree wants to merge 3 commits intojenkinsci:masterfrom
Conversation
|
Any chance you could share your build? I'd like to test it. |
|
Hi Kerrhome, Yes, we have a build branch that you can check. see : |
|
I believe this looks good. From #36 (comment): "Hi, I'm no longer interested in this plugin and mainly I don't have any time for testing of the changes and releasing of a new version. Please become a maintainer and ask for the permissions. https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin" Any chance you're prepared to do that? |
|
Any way to get the build artifact for this? |
|
@yitshakyarom, yes simple git clone https://github.com/AltranManatree/cppcheck-plugin/tree/jenkins-35096_Altran_cppcheck_plugin_pipeline_support and run "mvn install" |
|
Hi,
I have never worked with Maven, and it seems that I have some security issue on my laptop preventing some part of it…
When do you expect this to be merged into the plug in main branch? Is there an active maintainer for this plug-in?
Thanks
Yitzik
From: kumbasar [mailto:notifications@github.com]
Sent: Friday, October 20, 2017 8:45 AM
To: jenkinsci/cppcheck-plugin
Cc: Yitshak Yarom; Mention
Subject: Re: [jenkinsci/cppcheck-plugin] Jenkins 35096 altran cppcheck plugin pipeline support (#37)
@yitshakyarom<https://github.com/yitshakyarom>, yes simple git clone https://github.com/AltranManatree/cppcheck-plugin/tree/jenkins-35096_Altran_cppcheck_plugin_pipeline_support and run "mvn install"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#37 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AeRVLZT3lQmjjYoYWHdhelKfYX1CreExks5suDNvgaJpZM4PBhCk>.
|
|
I'm using this with Jenkins 2.89.2 and while it does give us the summary block on the individual build pages, if we click on the link to drill down into the cppcheck data, I get the following screen (pipeline and non-pipeline builds result in the same): Does anyone else see this? |
|
Looks like this is the bug: https://issues.jenkins-ci.org/browse/JENKINS-41704 |
|
I solved the conflicts and made fixes in pull request #39 |
Add support for ccpcheck pipeline jenkins 2.0
Note:
Another feature branch, jenkins-35096_cppcheck_plugin_pipeline_support already exists, but due to the fact it is still open in Jenkins jira. We are pushing our finished working cppCheck plugin for review.
Our plugin has been tested in our working environment, and is working correctly in jenkins V2 pipeline.
As an addition, the step can be called as follows:
instead of
step([$class: 'CppcheckPublisher', allowNoReport: false, displayAllErrors: true, displayErrorSeverity: false, displayInformationSeverity: false, displayNoCategorySeverity: false, displayPerformanceSeverity: false, displayPortabilitySeverity: false, displayStyleSeverity: false, displayWarningSeverity: false, failureThreshold: '', healthy: '', ignoreBlankFiles: false, newFailureThreshold: '', newThreshold: '', numBuildsInGraph: 0, pattern: 'cppcheck.xml', severityError: true, severityInformation: true, severityNoCategory: true, severityPerformance: true, severityPortability: true, severityStyle: true, severityWarning: true, threshold: '', unHealthy: '', xSize: 500, ySize: 200])