Difference between revisions of "Continuous Integration: Developer"

From Gcube Wiki
Jump to: navigation, search
(POM version on master)
Line 3: Line 3:
  
 
When a gCube release is declared open by the [[Continuous_Integration:_Releases_Manager#Responsibilities| Release Manager]] and until it is declared close, the artifact version in the POM on master MUST NOT have the -SNAPSHOT suffix.
 
When a gCube release is declared open by the [[Continuous_Integration:_Releases_Manager#Responsibilities| Release Manager]] and until it is declared close, the artifact version in the POM on master MUST NOT have the -SNAPSHOT suffix.
 +
 +
= Dependencies' version =
 +
The dependencies listed on the pom must be:
 +
* non SNAPSHOT, if a fixed version is requested. E.g.:
 +
** 1.0
 +
* a range with the lower limit without the SNAPSHOT qualifier. E.g.:
 +
** [1.0, 1.3]
 +
** [1.0, 1.3-SNAPSHOT)
 +
** [1.0, 2.0]
 +
** [1.0, 2.0-SNAPSHOT)
  
 
= Tagging Master =
 
= Tagging Master =

Revision as of 21:26, 20 September 2019

POM version on master

Technically, the master branch must be releasable at any time.

When a gCube release is declared open by the Release Manager and until it is declared close, the artifact version in the POM on master MUST NOT have the -SNAPSHOT suffix.

Dependencies' version

The dependencies listed on the pom must be:

  • non SNAPSHOT, if a fixed version is requested. E.g.:
    • 1.0
  • a range with the lower limit without the SNAPSHOT qualifier. E.g.:
    • [1.0, 1.3]
    • [1.0, 1.3-SNAPSHOT)
    • [1.0, 2.0]
    • [1.0, 2.0-SNAPSHOT)

Tagging Master

When the gCube release is declared close by the Release Manager and if the release includes a new version of a component, the developer must tag the master branch.

Creating a Release from the Tag

See Released Tags.

Back to the CI guide.