Difference between revisions of "SCM tools"
| Line 3: | Line 3: | ||
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). | 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). | ||
| − | [[Category:D4.1]] | + | [[Category:D4.1 Software Release Procedure and Tools]] |
Revision as of 17:42, 24 September 2015
GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites) that evolves continuously, transforming the system version by version. 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 their 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).
