[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
John McCabe commented on JENKINS-15801 Allow root of relative paths to be specified I had a look at https://issues.jenkins-ci.org/browse/JENKINS-14064 again after your comment @Ulli; I'd seen it before when I was searching for a possible solution. It's a similar issue but, as far as I can see, solving that would be a lot more difficult than this suggestion 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Ulli Hafner commented on JENKINS-15801 Allow root of relative paths to be specified @Joakim: shouldn't this work when you are using the new GCC parser that works in conjunction with make? (This still needs to be refactored, see JENKINS-14064). 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Joakim Plate commented on JENKINS-15801 Allow root of relative paths to be specified I would have thoughts so. But maybe it is because i execute the directory change (make -C) directly from the bash script instead of inside another make. 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Joakim Plate commented on JENKINS-15801 Allow root of relative paths to be specified Have similar issue. Doing unit tests on submodules of a project with the following structure. file.c test/makefile Where makefile refere to parent directory objects. To start the build i issue something like: make -C test 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Joakim Plate commented on JENKINS-15801 Allow root of relative paths to be specified Having similar issue here. Want to build unit tests with the following structure: file.c test/makefile makefile refer to ../file.c to build. jenkings build is kicked off like: make -C test 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Joakim Plate edited a comment on JENKINS-15801 Allow root of relative paths to be specified deleted duplicate 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
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
