# Git clone directory

**URL:** <https://www.finalbuilder.com/forums/t/git-clone-directory/5255>\
**Category:** Discussion\
**Created:** [October 15, 2014, 11:17am UTC](https://www.finalbuilder.com/forums/t/git-clone-directory/5255 "2014-10-15T11:17:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scoobydoo](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/dec6dc/32.png) [@scoobydoo](https://www.finalbuilder.com/forums/u/scoobydoo)\
**Post date:** [October 15, 2014, 11:17am UTC](https://www.finalbuilder.com/forums/t/git-clone-directory/5255/1 "2014-10-15T11:17:45Z")

</div>

Is there a way to specify that the build files are cloned to a specific folder?&nbsp;Our project is setup to reference another projects directory via a relative path.  
  
For example we have the following structure;  
  
-CommonProject  
-Project1  
-Project2  
  
Project1 & Project2 refer to files within CommonProject  
  
Currently the project is cloned into&nbsp;c:\ci\_ws\ws\13\Project1 type structure and obviously relative path names will not work. What i need is for the clone to  
be placed into something like c:\ci\_ws\ws\Project1 so that it can access&nbsp;c:\ci\_ws\ws\CommonProject etc  
  
Thanks

---

<div class="post-metadata">

**Author:** ![peter.toms](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/df788c/32.png) [@peter.toms](https://www.finalbuilder.com/forums/u/peter.toms)\
**Post date:** [October 16, 2014, 12:39pm UTC](https://www.finalbuilder.com/forums/t/git-clone-directory/5255/2 "2014-10-16T12:39:46Z")

</div>

Hi Scoobydoo, thank you for your post. &nbsp;  
  
We have a way to clone repositories to specific folders, this usecase is covered by the repository rules feature ([more details on repository rules](http://wiki.finalbuilder.com/display/continua/Repository+Rules)) and is accessible within the stage options dialogue. &nbsp;You can use the syntax $Source.REPONAMEHERE$ \> Source\MyCustomFolder.  
  
Currently the output (artifacts etc) from a configuration cannot be used as the inputs to another configuration (we have items on our backlog which address this type of use-case).  
  
Another option could be to combine your projects into a single configuration which builds all the required sources in the required sequence (you can use [repository scoping](http://wiki.finalbuilder.com/display/continua/Repository+Scope)&nbsp;here to make the required repositories accessible depending on your requirements).&nbsp;  
  
Please note that a builds workspace folder is intended to be transient (for the life of the build), configuration outputs should be registered as a [build artifact](http://wiki.finalbuilder.com/display/continua/Artifacts)).
