|
||||||||
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-10415) File not found when run... pyrogx1...@gmail.com (JIRA)
- [JIRA] (JENKINS-10415) File not found whe... pyrogx1...@gmail.com (JIRA)
- [JIRA] (JENKINS-10415) File not found whe... pyrogx1...@gmail.com (JIRA)
This don't think this problem was fixed correctly.
The root of the problem is as @miked described http://jenkins.361315.n4.nabble.com/Only-first-module-out-of-multiple-subversion-modules-is-built-td2281875.html
It actually makes it kind of silly to configure a free form project with this bug.
Consider this:
I make 2 svn checkouts svn://foo and svn://bar
because svn://foo was checked out first, all the files under svn://bar need to be referenced ../bar/file or $WORKSPACE/bar/file
Its ugly to have all these $WORKSPACE references all over the config. The correct thing to occur is to have every always relative to $WORKSPACE, this way to access files in svn://foo you just use foo/file and for svn://bar use bar/file
I don't have time at the moment to test this in the latest version of Jenkins. I'll create a bug if I can repo this and get around to it.