Difference between revisions of "Release Integration"

From Gcube Wiki
Jump to: navigation, search
(Preliminary steps)
(Preliminary steps)
Line 7: Line 7:
 
* Deploy the SNAPSHOT version on gcube-snapshots repository
 
* Deploy the SNAPSHOT version on gcube-snapshots repository
 
* Make sure the Git repository of the component is set up with a  working [https://wiki.gcube-system.org/gcube/Gitea/Jenkins:_Setting_up_Webhooks CI webhook]
 
* Make sure the Git repository of the component is set up with a  working [https://wiki.gcube-system.org/gcube/Gitea/Jenkins:_Setting_up_Webhooks CI webhook]
* Make sure the [https://wiki.gcube-system.org/gcube/Cloning_Git_Repository#Set_up_SCM_Connection scm section] is present in your pom
+
* Make sure the [https://wiki.gcube-system.org/gcube/Cloning_Git_Repository#Set_up_the_SCM_Connection scm section] is present in your pom
  
 
= Release Preparation =
 
= Release Preparation =

Revision as of 17:24, 24 November 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
  • Make sure the scm section is present in your pom

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.