Warnings-Plugin: How to access the path of current workspace?

[schneim]

Hello,

I have created a custom warning parser. This works quite well. However, I have trouble to display the content of the source files.

I found out the path in the warning is only relative to the workspace path, e.g.  $WORKSPACE/src/file.c 

But for displaying the source file, the plugin requires the full path.

The question is, how to find the workspace path to concatenate it with the file path inside the groovy script.

import hudson.plugins.warnings.parser.Warning

String workspace = getWorkspacePath()
String fileName = matcher.group(1)

String fullPath = workspace+fileName

String lineNumber = matcher.group(2)
String category = matcher.group(3)
String message = matcher.group(4)

return new Warning(fullPath, Integer.parseInt(lineNumber), "Dynamic Parser", category, message);

Any way to find out the value for the workspace or some other solution available?

Thanks

[Strausser, Barrett]

You could probably do $JenkinsHome + "/jobs/" + $WorkSpace

[Ulli Hafner]

Actually, a relative path (starting from the workspace root) should be resolved automatically. Does this not work in your case?

Ulli

[Markus Schneider]

Hello Ulli,

Yes the relative path  does not work for me. The tmp files are generated, but are empty. 

Do I need a special configuration?

Markus

[Markus Schneider]

I have tried it, but the parser throughs an error not knowing "$JenkinsHome"  string. 

[Ulli Hafner]

Hmm, I thought that the files should contain at least the exception string.

Can you please provide some more information?

What is your workspace path? Can you provide an example of a warning from the build console log? What is the corresponding warning result in warnings-[yourparsername].xml in the build folder? Is the path expanded there? 

Thanks, Ulli

[Markus Schneider]

Hi Ulli,

thanks for your help. Here is some more information:

Jenkins: V1.493

Warnings-Plugin: V4.18

Static Analysis Utilities: V1.48

OS: Windows XP

Workspace Path: C:\programme\Jenkins\test-ci\workspace

Example Warning:   "..\..\..\src\test.c", line 199: warning #550-D: variable "test" was set but never used

Parsed result  in parser configuration page is:

file name: src\test.c

line number: 199

category: #550-D

Project configuration uses "Scan workspace files"  with pattern **/*.log 

From warnings.xml:

<fileName>src/test.c</fileName>

<pathName>src</pathName>

-> path is not expanded in xml

Thanks,

Markus 

--

Markus Schneider

markus.s...@jemm.de

[Ulli Hafner]

I see, that can't work. 

Where is the src folder located? 

C:\programme\Jenkins\test-ci\workspace\src?

My plug-in concatenates the workspace path and the found path in the warning, which results in your case to C:\programme\Jenkins\test-ci\workspace\..\..\..\src\test.c

A simple solution would be to strip off the relative path section in your groovy parser so that the concatenation works.

Ulli

[Markus Schneider]

Hi,

Actually this what I have done in the regex. 

As you can see below, the groovy output has removed the relative path section. 

However, there is no concatenation with the workspace path:

C:\programme\Jenkins\test-ci\workspace

Can I do some debugging? Which class is appending the complete path?

Markus

[Markus Schneider]

Hi Ulli,

i have changed the path to the file in the warning.

It looks now like this:  "src\test.c", line 199: warning #550-D: variable "test" was set but never used

However, the path is not expanded.

Any other suggestions, what I can try?

Thanks,

Markus

--

Markus Schneider

markus.s...@jemm.de

[Markus Schneider]

Hi Ulli,

I have done some debugging and solved my issues:

1) Empty tmp source file, without any log statement why it is emtpy.

Reason: In my setups the default encoding was not set.  This caused an exception in the class HealthAwareRecorder.java in 

private void print(final FileOutputStream outputStream, final String message,

            final Object... arguments) throws IOException {

        IOUtils.write(String.format(message, arguments), outputStream, getDefaultEncoding());

    }

The default encoding was an empty string and therefore the write function threw the IOException "Unknown Encoding".

This resulted in jumping out of the logging function to print the statement, that the path to the source file is wrong.

Fixed by setting the Default Encoding in the configuration setting to "UTF-8"

2) Relative Path not expanded

Fixed by setting the corresponding configuration option in the extended section.  Stupid me, not seeing it before.

Thanks,

Markus   

--

Markus Schneider

markus.s...@jemm.de

[Ulli Hafner]

Hi Markus,

thanks for debugging. can you please create a new bug report for problem 1) I think I need to avoid that exception so that it is clear why the source could not be written… 

Ulli

[Markus Schneider]

Done: https://issues.jenkins-ci.org/browse/JENKINS-16222

--

Markus Schneider

markus.s...@jemm.de