[JIRA] (JENKINS-42613) Cppcheck publisher has no access to source files (experimental version for pipeline)

8 views
Skip to first unread message

dominik.machaj@gmail.com (JIRA)

unread,
Mar 9, 2017, 4:52:01 AM3/9/17
to jenkinsc...@googlegroups.com
Dominik Machaj created an issue
 
Jenkins / Bug JENKINS-42613
Cppcheck publisher has no access to source files (experimental version for pipeline)
Issue Type: Bug Bug
Assignee: Marco Steffan
Components: cppcheck-plugin, pipeline
Created: 2017/Mar/09 9:51 AM
Priority: Major Major
Reporter: Dominik Machaj

Experimental plugin with publishing cppcheck results for pipeline has no acces to source files located in cppcheck report.

After clicking filename the following message is displayed:

Can't access the file: Can't read file: correct file path

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

dominik.machaj@gmail.com (JIRA)

unread,
Mar 9, 2017, 4:55:02 AM3/9/17
to jenkinsc...@googlegroups.com
Dominik Machaj updated an issue
Change By: Dominik Machaj
Experimental plugin with publishing cppcheck results for pipeline has no acces to source files located in cppcheck report.

After clicking filename the following message is displayed:

Can't access the file: Can't read file: correct file path C:%5Cjenkins%5Cworkspace%5CbuildSpace%5CexampleFile.cpp

andrew.bayer@gmail.com (JIRA)

unread,
Feb 26, 2018, 4:29:06 PM2/26/18
to jenkinsc...@googlegroups.com

ilya.ilba@gmail.com (JIRA)

unread,
Dec 5, 2019, 8:31:03 PM12/5/19
to jenkinsc...@googlegroups.com

ilya.ilba@gmail.com (JIRA)

unread,
Dec 5, 2019, 8:32:03 PM12/5/19
to jenkinsc...@googlegroups.com

ilya.ilba@gmail.com (JIRA)

unread,
Dec 6, 2019, 6:25:05 AM12/6/19
to jenkinsc...@googlegroups.com
Ilya Ilba started work on Bug JENKINS-42613
 
Change By: Ilya Ilba
Status: Open In Progress

ilya.ilba@gmail.com (JIRA)

unread,
Dec 6, 2019, 6:26:03 AM12/6/19
to jenkinsc...@googlegroups.com

ilya.ilba@gmail.com (JIRA)

unread,
Dec 6, 2019, 6:27:03 AM12/6/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages