Difference between revisions of "SCM tools"
| Line 1: | Line 1: | ||
GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a central Software Configuration System (a.k.a. SCM [http://en.wikipedia.org/wiki/Software_configuration_management]) is made available (see section [[gcube subversion repository|gCube Subversion Repository]] to developers for storing source code of all gCube components. | GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a central Software Configuration System (a.k.a. SCM [http://en.wikipedia.org/wiki/Software_configuration_management]) is made available (see section [[gcube subversion repository|gCube Subversion Repository]] to developers for storing source code of all gCube components. | ||
| + | |||
| + | Currently, there exist only one central source code's repository, described in section [[gcube subversion repository|gCube Subversion Repository]], used by all gCube System's components. | ||
| + | |||
| + | For the future, we are thinking to use a distributed source repository software (like Git [http://git-scm.com/]) that would add more flexibility for developers having multiple repository nodes (e.g. one for each organization). | ||
Revision as of 17:44, 12 January 2012
GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a central Software Configuration System (a.k.a. SCM [1]) is made available (see section gCube Subversion Repository to developers for storing source code of all gCube components.
Currently, there exist only one central source code's repository, described in section gCube Subversion Repository, used by all gCube System's components.
For the future, we are thinking to use a distributed source repository software (like Git [2]) that would add more flexibility for developers having multiple repository nodes (e.g. one for each organization).
