Difference between revisions of "Release Integration"

From Gcube Wiki
Jump to: navigation, search
(Release Preparation)
Line 14: Line 14:
 
* 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
 
** remember that the CHANGELOG.md file must have the current release tag and the current version tag
 
** remember that the CHANGELOG.md file must have the current release tag and the current version tag
* Remove the snapshot from the master branch
+
* Remove the snapshot from the component master branch
 
* Create a new subticket of gCube Release Next master ticket: https://support.d4science.org/issues/17579
 
* Create a new subticket of gCube Release Next master ticket: https://support.d4science.org/issues/17579
 
** The subject ticket must uniquely identify the component
 
** The subject ticket must uniquely identify the component

Revision as of 08:41, 19 June 2020

Preliminary 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 integrate a new component in a gCube release, some preparatory steps (performed by the Developer) are needed:

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