[JIRA] (JENKINS-54246) publishCppcheck in pipeline fails job not stage

9 views
Skip to first unread message

thomas.sondergaard@karoshealth.com (JIRA)

unread,
Oct 25, 2018, 5:56:02 AM10/25/18
to jenkinsc...@googlegroups.com
tsondergaard created an issue
 
Jenkins / Bug JENKINS-54246
publishCppcheck in pipeline fails job not stage
Issue Type: Bug Bug
Assignee: Marco Steffan
Components: cppcheck-plugin
Created: 2018-10-25 09:55
Priority: Minor Minor
Reporter: tsondergaard

When cppcheck finds an error publishCppcheck writes the following in the log:

[Cppcheck] Starting the cppcheck analysis.
[Cppcheck] Processing 1 files with the pattern 'cppcheck_report.xml'.
[Cppcheck] Setting build status to FAILURE since total number of issues '1' exceeds the threshold value '0'.
[Cppcheck] Ending the cppcheck analysis.

but the stage it runs in is not marked as failed. I have tried using publishCppcheck in both steps and post sections and it makes no difference.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

thomas.sondergaard@karoshealth.com (JIRA)

unread,
Apr 27, 2020, 5:42:03 AM4/27/20
to jenkinsc...@googlegroups.com
tsondergaard updated an issue
Change By: tsondergaard
Priority: Minor Critical
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

thomas.sondergaard@karoshealth.com (JIRA)

unread,
Apr 27, 2020, 5:48:02 AM4/27/20
to jenkinsc...@googlegroups.com
tsondergaard commented on Bug JENKINS-54246
 
Re: publishCppcheck in pipeline fails job not stage

This is still a problem. Is there anything I can do to help?

thomas.sondergaard@karoshealth.com (JIRA)

unread,
Apr 27, 2020, 8:44:03 AM4/27/20
to jenkinsc...@googlegroups.com

Some information that I believe is relevant:

Specifically it looks from the junit-plugin pull request that something like this will mark the step failed:

FlowNode node = getContext().get(FlowNode.class);
node.addOrReplaceAction(new WarningAction(Result.FAILURE).withMessage("<Some explanation here>"));

I think stuff like that simply has to be added in CppcheckPublisher.perform().
Reply all
Reply to author
Forward
0 new messages