[JIRA] (JENKINS-15801) Allow root of relative paths to be specified

[j...@assen.demon.co.uk (JIRA)]

John McCabe created JENKINS-15801 Allow root of relative paths to be specified Issue Type: Improvement Assignee: Ulli Hafner Components: warnings Created: 12/Nov/12 10:51 AM Description: Due to the way that my system is built, I've found I need to set up a custom Jenkins workspace but, in the build step, I'm launching a python script that moves to a specific location before starting to compile. Although I've got "resolve relative paths" checked it doesn't seem to be working properly; the files created in jobs/<myjob>/builds/<date>/workspace-files are all empty. I suspect this is caused by the odd way out code is built. The warnings tend to be of the form: ../../<a>/<b>/<c>/<d>/<e>.c:329: warning: empty body in an else-statement This is relative to the location where I run my build script, but that is somewhere down the path from the Jenkins workspace (e:\work\Jenkins). My suggestion is therefore to allow a root path to be used by the Compiler Warnings plugin when trying to resolve relative paths. If I were able to specify the root, let's say "E:\Work\Jenkins\<p1>\<p2>\<p3>", (where p1..p3 are replaced by my folder names) it should be easy for the warnings plugin to resolve "../../<a>/<b>/<c>/<d>/<e>.c" to "E:\Work\Jenkins\<p1>\<a>\<b>\<c>\<d>\<e>.c" correctly. Environment: Windows 7 Project: Jenkins Priority: Major Reporter: John McCabe

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira