[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files

ullrich.hafner@gmail.com (JIRA)

unread,

Nov 7, 2018, 8:33:02 AM11/7/18

to jenkinsc...@googlegroups.com

Ulli Hafner updated an issue

Jenkins /

JENKINS-48802

Possibility to add/change the path that used to display source files

Change By:	Ulli Hafner
Component/s:	warnings-ng-plugin
Component/s:	warnings-plugin

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jfaust@tsunamit.com (JIRA)

unread,

Jan 21, 2019, 4:53:01 PM1/21/19

to jenkinsc...@googlegroups.com

Jason Faust commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

As a additional add to this request, can the possible path prefixes to check be a collection? For example, The TagList parser reports hits in source files, without indicating if they in the main directory or the test directory, and letting the file name resolution part look in many spots would be useful to solving this issue.

Add Comment

ullrich.hafner@gmail.com (JIRA)

unread,

Feb 27, 2019, 5:46:03 PM2/27/19

to jenkinsc...@googlegroups.com

Ulli Hafner started work on

JENKINS-48802

Change By:	Ulli Hafner
Status:	Open In Progress

Add Comment

matthieu.brucher@gmail.com (JIRA)

unread,

May 3, 2019, 5:44:02 AM5/3/19

to jenkinsc...@googlegroups.com

Matthieu Brucher commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

I have a similar issue. I generate a checkstyle file inside a docker container with some paths, but using relative paths there makes the upload break later due to Warnings NG not capable of reconciling the files.

Add Comment

ullrich.hafner@gmail.com (JIRA)

unread,

May 3, 2019, 6:44:01 AM5/3/19

to jenkinsc...@googlegroups.com

Ulli Hafner commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

How do you invoke CheckStyle? CheckStyle normally does export absolute paths already.

Add Comment

matthieu.brucher@gmail.com (JIRA)

unread,

May 3, 2019, 7:43:01 AM5/3/19

to jenkinsc...@googlegroups.com

Matthieu Brucher commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

The file is generated from eslint inside a docker container. As such the paths will be different than the ones from the workspace (not even talking about the fact that there are several containers in flight, each of them having only a part of the workspace).

Add Comment

ullrich.hafner@gmail.com (JIRA)

unread,

May 3, 2019, 10:31:04 AM5/3/19

to jenkinsc...@googlegroups.com

Ulli Hafner commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

Hmm, but how should adding a source code path help in your case? The files are fetched from the agent that contains the checkstyle.xml file. Is your workspace outside of the docker container? And how does eslint find the sources to check?

Add Comment

matthieu.brucher@gmail.com (JIRA)

unread,

May 3, 2019, 10:44:03 AM5/3/19

to jenkinsc...@googlegroups.com

Matthieu Brucher commented on

JENKINS-48802

Re: Possibility to add/change the path that used to display source files

eslint is run inside the container, the container itself is built at the beginning of the pipeline. As I can't assume that the Jenkins slave have all the required tools to run eslint, the proper way to go was to use a container that would retrieve the required modules.

Just adding a way to reconnect the two paths would be enough, as the path inside the container (also used for the unit tests) is just a fraction of the actual workspace path. Basically just adding "folder/" as "folder" would be where I built the container. The Jenkins pipeline itself is run in the parent of "folder", I suspect that's why the checker cannot figure out where the files actually are.