Difference between revisions of "Continuous Integration: Developer"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Tagging Master) |
Manuele.simi (Talk | contribs) |
||
| Line 9: | Line 9: | ||
= Creating a Release from the Tag= | = Creating a Release from the Tag= | ||
See [[Tags#Released_Tags| Released Tags]]. | See [[Tags#Released_Tags| Released Tags]]. | ||
| + | |||
| + | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | ||
Revision as of 16:25, 30 May 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.
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.
