Difference between revisions of "Building tools"

From Gcube Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
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 subverion repository|gCube Subversion Repository]] to developers for storing source code of all gCube components.
+
The [[SCM tools|gCube source code repository]] is used as input from the [[Continuous Integration procedure|Continuous Integration procedure]] that run automatic periodic builds of the entire gCube System in order to early identify integration issues among system's components. To accomplish this task the gCube team make use of a set of tools to automatize the building of code:
 +
* the [[ETICS|ETICS System]] to keep the configurations of the all components, express dependencies among components, define build and test commands for each component
 +
* the [[Building Infrastructure|Building Infrastructure]] that periodically download project configurations and build commands from ETICS and run a build of the entire project
 +
* the [[BTRT|BTRT]] is the access site for all logs, reports and artifacts produced by builds executed on the Testing Infrastructure
 +
 
 +
 
 +
For each of this tools, we provide a detailed description in this section.

Latest revision as of 11:33, 13 January 2012

The gCube source code repository is used as input from the Continuous Integration procedure that run automatic periodic builds of the entire gCube System in order to early identify integration issues among system's components. To accomplish this task the gCube team make use of a set of tools to automatize the building of code:

  • the ETICS System to keep the configurations of the all components, express dependencies among components, define build and test commands for each component
  • the Building Infrastructure that periodically download project configurations and build commands from ETICS and run a build of the entire project
  • the BTRT is the access site for all logs, reports and artifacts produced by builds executed on the Testing Infrastructure


For each of this tools, we provide a detailed description in this section.