Difference between revisions of "Release Integration"
From Gcube Wiki
| Line 2: | Line 2: | ||
In order to integrate a new component in a gCube release, some '''preparatory steps''' (performed by the Developer) are needed: | In order to integrate a new component in a gCube release, some '''preparatory steps''' (performed by the Developer) 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 | |
| Line 14: | Line 14: | ||
The rules to attach a component to a new gCube Release are the following ones: | The rules to attach a component to a new gCube Release are the following ones: | ||
| − | + | * 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 | |
| − | + | * 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 | ||
| − | + | * 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. | |
Revision as of 08:37, 19 June 2020
Release Preparation
In order to integrate a new component in a gCube release, some preparatory steps (performed by the Developer) 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 Integration
Once the preparation steps are completed, the integration phase can be started.
The rules to attach a component to a new gCube Release are the following ones:
- 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 master branch
- Create a new subticket of gCube Release Next master ticket: 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.
