Difference between revisions of "Software Integration and Distribution: Overview"

From Gcube Wiki
Jump to: navigation, search
Line 2: Line 2:
  
 
This section documents all the procedures and tools used for releasing the gCube system. It is intended as the central access point to information about the integration, validation, and distribution of the system for developers, software testers, release managers, and for any other actor involved in the development of the system (see [[Software_Integration_and_Distribution:_Roles]]).
 
This section documents all the procedures and tools used for releasing the gCube system. It is intended as the central access point to information about the integration, validation, and distribution of the system for developers, software testers, release managers, and for any other actor involved in the development of the system (see [[Software_Integration_and_Distribution:_Roles]]).
 +
 
Given the large size of the gCube system, its high degree of modularity and the number of developers involved in the implementation, a set of procedures that formalize and simplify the integration, test, documentation and distribution of the software have been defined. These procedures coordinate the actions and the timing of the different actors to achieve the desired result. Section [[Release Procedures]] provides a detailed description of each procedure by listing actors and their responsibilities for each step of each procedure.
 
Given the large size of the gCube system, its high degree of modularity and the number of developers involved in the implementation, a set of procedures that formalize and simplify the integration, test, documentation and distribution of the software have been defined. These procedures coordinate the actions and the timing of the different actors to achieve the desired result. Section [[Release Procedures]] provides a detailed description of each procedure by listing actors and their responsibilities for each step of each procedure.
 
 
Activities in release procedures are highly automated and supported by several tools described in section [[Release Tools|Release Tools]]. Different tools offer support in different phases of the integration, test and distribution process:
 
* configuration of source code ([[SCM tools]]);
 
* release preparation phase ([[Redmine]]);
 
* software integration phase ([[ETICS]], [[BTRT]], [[Building Infrastructure]])
 
* testing phase ([[Static Code Analysis|Checkstyle]], [[Static Code Analysis|Findbugs]], [[ETICS]], [[Testing Infrastructure]])
 
* documentation of the system ([[gCube System documentation wiki|Wikimedia]]);
 
* distribution of the system ([[gCube Web Site and Distribution Site|gCube Distribution Site]]).
 
  
  

Revision as of 16:51, 28 September 2015


This section documents all the procedures and tools used for releasing the gCube system. It is intended as the central access point to information about the integration, validation, and distribution of the system for developers, software testers, release managers, and for any other actor involved in the development of the system (see Software_Integration_and_Distribution:_Roles).

Given the large size of the gCube system, its high degree of modularity and the number of developers involved in the implementation, a set of procedures that formalize and simplify the integration, test, documentation and distribution of the software have been defined. These procedures coordinate the actions and the timing of the different actors to achieve the desired result. Section Release Procedures provides a detailed description of each procedure by listing actors and their responsibilities for each step of each procedure.


Release Roles


Release Tools

Release Procedures


Test Plan


Naming Conventions

Release Log