Difference between revisions of "Continuous Integration: Developer"
Manuele.simi (Talk | contribs) (→Dependencies' version) |
Manuele.simi (Talk | contribs) (→Dependencies' version) |
||
| Line 5: | Line 5: | ||
= Dependencies' version = | = Dependencies' version = | ||
| − | The dependencies listed on the pom must be: | + | The dependencies listed on the pom must be one of the following: |
| − | + | 1) non SNAPSHOT, if a fixed version is requested. E.g.: | |
** 1.0 | ** 1.0 | ||
| − | + | ||
| + | OR | ||
| + | |||
| + | 2) a range with the lower limit without the SNAPSHOT qualifier. E.g.: | ||
** [1.0, 1.3] | ** [1.0, 1.3] | ||
** [1.0, 1.3-SNAPSHOT) | ** [1.0, 1.3-SNAPSHOT) | ||
Revision as of 17:52, 2 October 2019
Contents
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 one of the following: 1) non SNAPSHOT, if a fixed version is requested. E.g.:
- 1.0
OR
2) 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)
For instance, the [1.0, 2.0-SNAPSHOT) will resolve against any version prior to 2.0-SNAPSHOT. Using [1.0, 2.0) will instead INCLUDE 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.
