[
https://issues.jenkins-ci.org/browse/JENKINS-11379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162483#comment-162483
]
knalli commented on JENKINS-11379:
----------------------------------
I can confirm this issue. Same situation, is broken. However, workaround is
easy: Update the created new job.
> "Local module directory" not copied from trunk project when creating a
> feature branch
> -------------------------------------------------------------------------------------
>
> Key: JENKINS-11379
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11379
> Project: Jenkins
> Issue Type: Bug
> Components: svnmerge
> Environment: Windows Server 2003 R2 with TomCat
> Reporter: David Schamber
> Assignee: Kohsuke Kawaguchi
> Priority: Minor
>
> 1. Created a trunk project in Jenkins and verified that it built successfully.
> 2. Created a feature project through Jenkins
> 3. Attempted to build the branch only to find that Jenkins couldn't locate
> the necessary batch files.
> Upon further investigation I noticed that Jenkins was checking out the files
> to a subdirectory (same name as branch) of the workspace instead of directly
> to the workspace folder like the trunk was doing. That's when I realized the
> the "Local module directory (optional)" setting for the branch didn't match
> the trunk. The trunk's option was set to '.', but the branch's option was
> empty. In order for a branch to build straightaway this setting should be
> copied from the trunk project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
