-
Improvement
-
Resolution: Duplicate
-
Minor
Original reporter ivananishchuk
Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic.
At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir.
More info on SO: http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git
- is related to
-
-
- Resolved
-
[JENKINS-32246] Is it absolutely necessary to keep full .git repository in the sub-projects?
| Description |
Original:
Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic. At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. [More info on SO](http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git) |
New:
Original reporter [~ivananishchuk] Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic. At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. [More info on SO](http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git) |
| Description |
Original:
Original reporter [~ivananishchuk] Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic. At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. [More info on SO](http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git) |
New:
Original reporter [~ivananishchuk] Can't we use, say, just one git directory for all of them? (Making them multiple working directories for a single git repository.) It would save a lot of disk space and internet traffic. At the very least, maybe we can use master-project's cloned repository as a remote for sub-projects? Local git clone uses hardlinks so the disk space and traffic would be preserved without changing how it looks inside each workdir. More info on SO: http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git |
| Component/s | New: git-plugin [ 15543 ] | |
| Component/s | Original: multi-branch-project-plugin [ 21127 ] |
| Labels | New: multibranch |
| Component/s | New: branch-api-plugin [ 18621 ] | |
| Component/s | New: scm-api-plugin [ 18054 ] |
| Component/s | Original: branch-api-plugin [ 18621 ] |
| Assignee | Original: Matthew DeTullio [ mjdetullio ] | New: Mark Waite [ markewaite ] |
| Component/s | New: branch-api-plugin [ 18621 ] |
| Assignee | Original: Mark Waite [ markewaite ] |
| Workflow | Original: JNJira [ 167831 ] | New: JNJira + In-Review [ 182861 ] |