Difference between revisions of "Release Integration"
From Gcube Wiki
(→Preliminary steps) |
|||
| Line 5: | Line 5: | ||
* Upgrade and test the component in development environment | * Upgrade and test the component in development environment | ||
* Deploy the SNAPSHOT version on gcube-snapshots repository | * Deploy the SNAPSHOT version on gcube-snapshots repository | ||
| − | * Add the maven-parent 1.1.0 to the component pom | + | * Add the maven-parent '''1.1.0''' to the component pom |
= Release Preparation = | = Release Preparation = | ||
Revision as of 09:52, 19 June 2020
Preliminary steps
In order to integrate a new component in a gCube release, The developer should perform some preliminary steps are needed:
- 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:
- 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
- Remove the snapshot from the component master branch
- Create a new subticket of "gCube Release Next" defined here: https://support.d4science.org/issues/17579
- The subject ticket must uniquely identify the component
- When the previos steps are completed the ticket can be set to Available state. The Release Manager is in charge of add all the Available ticket to the new Release.
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.
