The purpose of this page is to describe our git tagging conventions for LexEVS software that resides in github and how the git tags are used in the naming of the LexEVS artifacts. This will help users of the LexEVS PTEs to understand the git tags and resulting artifacts that are produced.
Convention
Our convention for naming artifacts will be to use the artifact name followed by the git tag and then the file extension. This convention will be used when creating artifacts for the PTEs.
- <artifact name>-<git tag>.file extension
NCI Tiers
Development Tier
When we deploy to NCI Development system, we will tag and name our artifacts in the following way:
- Git Tag
- <version>.SNAPSHOT.#
- Example: 1.4.1.SNAPSHOT.1
- Artifact Name
- artifact-<version>.SNAPSHOT.#.jar/war
- lexevs API
- lexbig-6.4.0.SNAPSHOT.1.jar
- extLib-6.4.0.SNAPSHOT.1.zip
- LexEVS-install-config-6.4.0.SNAPSHOT.1.xml
- LexEVS-install-6.4.0.SNAPSHOT.1.jar
- lexevs-remote (lexevs remote API)
- lexevs-remote-1.4.1.SNAPSHOT.1.war
- lexevs-service (CTS2)
- lexevs-service-1.4.1.SNAPSHOT.1.war
QA Tier
When we deploy to the NCI QA tier, we will tag and name our artifacts in the following way:
- Git Tag
- <version>.RC.#
- Example: 1.4.1.RC.1
- Artifact Name
- artifact-<version>.RC.#.jar/war
- lexevs API
- lexbig-6.4.0.RC.1.jar
- extLib-6.4.0.RC.1.zip
- LexEVS-install-config-6.4.0.RC.1.xml
- LexEVS-install-6.4.0.RC.1.jar
- lexevs-remote (lexevs remote API)
- lexevs-remote-1.4.1.RC.1.war
- lexevs-service (CTS2)
- lexevs-service-1.4.1.RC.1.war
STAGE and PRODUCTION Tiers
When we deploy to NCI STAGE and PRODUCTION tiers, we will tag and name our artifacts in the following way:
- Git Tag
- <version>.FINAL
- Example: 1.4.1.FINAL
- Artifact Name
- lexevs API
- lexbig-6.4.0.FINAL.jar
- extLib-6.4.0.FINAL.zip
- LexEVS-install-config-6.4.0.FINAL.xml
- LexEVS-install-6.4.0.FINAL.jar
- lexevs-remote (lexevs remote API)
- lexevs-remote-1.4.1.FINAL.war
- lexevs-service (CTS2)
- lexevs-service-1.4.1.FINAL.war