[ 
https://issues.jenkins-ci.org/browse/JENKINS-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162448#comment-162448
 ] 

Liam Staskawicz commented on JENKINS-13685:
-------------------------------------------

A few more details: The master node is on an OS X 10.6 machine, installed 
jenkins 1.462 via homebrew: 
https://github.com/mxcl/homebrew/blob/master/Library/Formula/jenkins.rb
                
> Git clean on Multi Configuration build requires re-clone of slave repo
> ----------------------------------------------------------------------
>
>                 Key: JENKINS-13685
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13685
>             Project: Jenkins
>          Issue Type: Bug
>          Components: git
>         Environment: OS X, Windows7, Linux. Jenkins 1.462
>            Reporter: Liam Staskawicz
>            Assignee: Nicolas De Loof
>              Labels: git, gitplugin
>
> I've just set up a Multi Configuration job: a master with no build 
> responsibilities & 3 slaves (mac, win, linux). I see that the master clones a 
> copy of the source repo into the root of one of the slave's workspace: 
> workspace/projectname/contentsofrepo.
> Then, the slave clones a separate copy of the same repo for its own purposes: 
> workspace/projectname/label/osx/contentsofrepo.
> I prefer to use the "Clean after checkout" option for my git projects, to 
> ensure a clean workspace on a fresh build. However, with this enabled the 
> master's git repo sees the slave's repo (again, located within the master's 
> copy) as a directory not tracked by git and removes it, meaning that when the 
> slave runs, it has to re-clone the entire repo, which takes about a half hour 
> for our project.
> I would expect the master & slave's copies of the repos to not overlap with 
> one another such that they could be cleaned independently of one another.

--
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

        

Reply via email to