Difference between revisions of "Continuous Integration: FAQ"
From Gcube Wiki
Manuele.simi (Talk | contribs) (Created page with "Q: '''What do I keep in a Git Repository?''' A: ...") |
Manuele.simi (Talk | contribs) |
||
| Line 2: | Line 2: | ||
A: | A: | ||
| − | ... | + | For a correct answer, we first need to point out a fundamental difference between SVN and Git: |
| + | |||
| + | * In SVN, there is one single repository, whose structure is equivalent to a file system. You can check out and work at any level of the SVN tree. | ||
| + | * In Git, there are several repositories, independent from each other. You need to clone an entire repository to work on its content. | ||
| + | |||
| + | Given that, a multi-module repository (i.e. a repositories with several modules not grouped in a reactor build of a parent pom) are strongly discouraged. Such repository would force a developer to clone the entire repo, regardless the module he/she would work on. Also Jenkins would be in the same situation: clone a full repo to then build just a small piece of it. | ||
Revision as of 02:34, 28 June 2019
Q: What do I keep in a Git Repository?
A: For a correct answer, we first need to point out a fundamental difference between SVN and Git:
- In SVN, there is one single repository, whose structure is equivalent to a file system. You can check out and work at any level of the SVN tree.
- In Git, there are several repositories, independent from each other. You need to clone an entire repository to work on its content.
Given that, a multi-module repository (i.e. a repositories with several modules not grouped in a reactor build of a parent pom) are strongly discouraged. Such repository would force a developer to clone the entire repo, regardless the module he/she would work on. Also Jenkins would be in the same situation: clone a full repo to then build just a small piece of it.
