Difference between revisions of "Release Integration"

From Gcube Wiki
Jump to: navigation, search
(Preliminary steps)
Line 1: Line 1:
 
= Preliminary steps =
 
= Preliminary steps =
  
In order to integrate a new component in a gCube release, The developer should perform some preliminary steps:
+
In order to develop a new component for gCube, the developer must perform the following steps:
  
 
* Upgrade and test the component in development environment
 
* Upgrade and test the component in development environment
Line 8: Line 8:
  
 
= Release Preparation =
 
= Release Preparation =
In order to integrate a new component in a gCube release, some '''preparatory steps''' (performed by the Developer) are needed:
+
In order to prepare a new component for the integration within a gCube release, the developer must perform the following steps:
  
 
* Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents
 
* Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents

Revision as of 13:35, 19 June 2020

Preliminary steps

In order to develop a new component for gCube, the developer must perform the following steps:

  • Upgrade and test the component in development environment
  • Deploy the SNAPSHOT version on gcube-snapshots repository
  • Add the maven-parent 1.1.0 to the component pom

Release Preparation

In order to prepare a new component for the integration within a gCube release, the developer must perform the following steps:

Once the preparation steps are completed, the integration phase can be started.

  • After the integration phase, the component master branch must be freezed until the release will be declared closed by Release Manager.