Build Merrit Integration Test docker images housed in merritt-docker. Push to ECR.
mock-merritt-it:dev
mrt-it-database:dev
mrt-it-database-audit-replic:dev
mrt-minio-it:dev
mrt-minio-it-with-content:dev
merritt-tomcat:dev
merritt-maven:dev
mrt-init
callback
mrt-database
Build Merritt Jar files. Push JAR to Code Artifact.
Libraries
mrt-core2:dev
mrt-zk:dev
mrt-cloud:dev
mrt-inventory-src:dev
[!NOTE]
pom.xml files will need to be modified to reference CodeArtifact.
The Merritt team will need to figure out how to tag appropriately for CodeArtifact.
Build Merritt Java Services. Push WAR to Code Artifact
mrt-ingest:dev
mrt-inventory:dev
mrt-store:dev
mrt-audit:dev
mrt-replic:dev
[!NOTE]
pom.xml files will need to be modified to reference CodeArtifact.
Public docker image for Merritt Services. Push to ECR.
5 Java servcies listed above
mrt-dashboard
[!NOTE]
the Dockerfiles for each of these services currently reside in merritt-docker.
These resources will be migrated into the service-specific code repo.
The Merritt team will need to figure out how to tag appropriately for CodeArtifact.
Merritt Lambda mrt-admin-lambda. Push to ECR. Lambda runs in the main account.
mysql-ruby-lambda
uc3-mrt-admin-common:dev
uc3-mrt-admin-lambda:dev
uc3-mrt-colladmin-lambda:dev
uc3-mrt-cognitousers:dev
simulate-lambda-alb
[!NOTE]
Would we need to continue to push to the main account ECR for Lambda purposes?
Merritt End to End test images mrt-integ-tests. Push to ECR.
Design
https://github.com/CDLUC3/mrt-doc/blob/main/design/aws-build/README.md
Objectives
Question for IAS
Build Merrit Integration Test docker images housed in merritt-docker. Push to ECR.
Build Merritt Jar files. Push JAR to Code Artifact.
Libraries
Build Merritt Java Services. Push WAR to Code Artifact
Public docker image for Merritt Services. Push to ECR.
Merritt Lambda mrt-admin-lambda. Push to ECR. Lambda runs in the main account.
Merritt End to End test images mrt-integ-tests. Push to ECR.
Soon to be deprecated java libraries
3rd party images that we trivvy scan