Difference between revisions of "Release Integration"

From Gcube Wiki
Jump to: navigation, search
(Preliminary steps)
(Release Preparation)
Line 18: Line 18:
 
** When the all these steps have been completed the ticket can be set to ''Available'' state.  
 
** When the all these steps have been completed the ticket can be set to ''Available'' state.  
  
Then, the '''Release Manager''' is in charge to add all the ''Available'' tickets to the new Release and the '''integration phase''' of the new release can start.
+
Then, the '''Release Manager''' is in charge to add all the ''Available'' tickets to the new Release and the '''integration phase''' of the release can start.
  
 
*During the integration phase, the master branch of each component under release must be frozen until the release is declared closed by Release Manager. As per feature branching policy, any work must be performed in a separate feature or fix branch.
 
*During the integration phase, the master branch of each component under release must be frozen until the release is declared closed by Release Manager. As per feature branching policy, any work must be performed in a separate feature or fix branch.

Revision as of 13:49, 19 June 2020

Preliminary steps

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

  • Make sure the maven-parent 1.1.0 is used as parent pom
  • Upgrade and test the component in the development environment
  • Deploy the SNAPSHOT version on gcube-snapshots repository
  • Make sure the Git repository of the component is set up with a working CI webhook

Release Preparation

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

Then, the Release Manager is in charge to add all the Available tickets to the new Release and the integration phase of the release can start.

  • During the integration phase, the master branch of each component under release must be frozen until the release is declared closed by Release Manager. As per feature branching policy, any work must be performed in a separate feature or fix branch.