Difference between revisions of "Release Tools"
From Gcube Wiki
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | gCube is a complex system developed in collaborative way by developers geographically separated and affiliated to several organization. Considering also the size of the gCube system (hundreds of components), it is vital the usage of proper tools to configure the source code and to manage the release process. | + | gCube is a complex system developed in collaborative way by developers geographically separated and affiliated to several organization. Considering also the size of the gCube system (hundreds of components), it is vital the usage of proper tools to configure the source code and to manage the release process. The tools allow the automation of several steps of the release process and communicate each other to assure a proper and seamless automation of gCube System releases in all their steps. |
| − | + | ||
| + | * [[Redmine|Tracking System]] | ||
| + | * [[Integration of Maven Components|Maven]] | ||
| + | ** [[Developing gCube Maven Components|gCube Maven Components]] | ||
| + | ** [[GCube_Maven_BOMs|gCube Maven BOMs]] | ||
| + | * [[Integration Infrastructure]] | ||
| + | ** [[gcube subversion repository|SVN Repository]] | ||
| + | ** [[GitHub|GitHub]] | ||
| + | ** [[ETICS|ETICS]] | ||
| + | ** [[BTRT|BTRT]] | ||
| + | ** [[gCube Web Site and Distribution Site|Distribution Sites]] | ||
| + | * [[Testing Infrastructure|Testing Infrastructure]] | ||
| + | * [[gCube System documentation wiki|Documentation]] | ||
Latest revision as of 13:10, 27 October 2016
gCube is a complex system developed in collaborative way by developers geographically separated and affiliated to several organization. Considering also the size of the gCube system (hundreds of components), it is vital the usage of proper tools to configure the source code and to manage the release process. The tools allow the automation of several steps of the release process and communicate each other to assure a proper and seamless automation of gCube System releases in all their steps.
