Naming Conventions
Naming convention for each component in zip are as follows:
$(release_component) = $(component name)-$(release_version).zip
where
$(component name) = one of component in installation component lists
$(release_version) = $(year).$(month).$(day).$(sub version)
$(year) = YYYY
$(month) = 01 - 12
$(day) = 01 - 31
$(sub version) = 1, 2, ....
Repositories
There are two types of repositories to store releases of all components:
- Artifactories
- File System
Artifactories
- Eagle R&D Artifactory (https://artifactory.devops.eagleinvsys.com/ui/repos/tree/General/rd-release-locall)
- Eagle PGH Artifactory (https://artifactory.k8s.eagleaccess.com/artifactory/webapp/#/artifacts/browse/tree/General/rd-release-virtual-pgh)
- Eagle Cloud Artifactory (https://eagleinvsys.jfrog.io/eagleinvsys/rd-release-cloud)
Artifactory Root URL for Components
The following are root urls for components.
- EagleInstaller component
- EagleInstaller
$(artifactory url)/EagleInstaller
- EagleML component
- EagleML
$(artifactory url)/EagleML
- EagleML-without-overlays
$(artifactory url)/EagleML-without-overlays
- EagleML+MC2
- All-services
$(artifactory url)/com/eagleinvsys/mc2
- All-services-without-overlays
$(artifactory url)/com/eagleinvsys/mc2
- MC2 Components
- Extract Service Rules
$(artifactory url)/extractservicerules
- Import Service Rules
$(artifactory url)/importservicerules
- EaglePy (component name = pypy)
$(artifactory url)/com/eagleinvsys/pypy
- pyruleservice
$(artifactory url)/com/eagleinvsys/pyruleservice
- extractservice
$(artifactory url)/com/eagleinvsys/eagleinvsys/eaglemc2s/eaglemc2s
- kafkaservice
$(artifactory url)/eagle-kafka-service/eagle-kafka-service
File System
The standard location from the file system is located in the following path for each monthly:
- The nest – "\\thenest\TFS_BUILD_PACKAGES\$(year)_$(Month)Release(FINAL)"
where:
$(year) = YYYY
$(Month) = January, February, ....