About Installation Components and Repositories

EagleML/MC2 teams release several components on a monthly basis. This page provides details on these components including naming conventions, artifactory, and repository details.

Installation Components

The following are the components released by EagleML/MC2 teams in a monthly basis.

EagleInstaller component
- EagleInstaller (component name = EagleInstaller)
EagleML component
- EagleML (component name = EagleML)
- EagleML-without-overlays (component name = EagleML-without-overlays)
EagleML+MC2
- All-services (component name = all-services)
- All-services-without-overlays (component name = all-services-without-overlays)
MC2 components
- Extract Service Rules (component name = extractservicerule)
- Import Service Rules (component name = importservicerule)
- EaglePy (component name = pypy)
- pyruleservice (component name = pyruleservice)
- extractservice (component name = extractservice)
- kafkaservice (component name = kafkaservice)

On this page

1 Installation Components
2 Naming Conventions
3 Repositories
4 Artifactories
5 Artifactory Root URL for Components
6 File System

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-local l)
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, ....

Currently only EagleInstaller, EagleML and EagleML-without-overlays are distributed to the file system.