GitLab

Cache Maven Repository during AWS Test Execution

See merge request osdu/platform/ci-cd-pipelines!21

A survey of 100 developers shows that most think this might be important to a
caching feature...

Because downloading maven dependencies every test is really a bear.

add Ibm provider

See merge request osdu/platform/ci-cd-pipelines!19

Add variables that AWS needs for elastic search

See merge request osdu/platform/ci-cd-pipelines!20

This will be added by individual services that need it, rather than blanketed
across all of them. Test jobs that do not require the aws-internal-test runner
(which runs inside the AWS VPC) can utilize the generic runners.

AWS ci/cd for Storage/Legal/Delivery services

See merge request osdu/platform/ci-cd-pipelines!18

Storage Service Variables

See merge request osdu/platform/ci-cd-pipelines!16

Trusted Azure Updates

See merge request osdu/platform/ci-cd-pipelines!15

Build Variables

See merge request osdu/platform/ci-cd-pipelines!14

Docker container Builds

See merge request osdu/platform/ci-cd-pipelines!13

Azure Build Variable Updates

See merge request osdu/platform/ci-cd-pipelines!12

Resolve "GitLab Ultimate License Scanning Format"

Closes #9

See merge request osdu/platform/ci-cd-pipelines!11

This is based on https://docs.gitlab.com/ee/user/compliance/license_compliance/#migration-from-license_management-to-license_scanning

Resolve "Make FOSSA NOTICE available on failure"

Closes #8

See merge request osdu/platform/ci-cd-pipelines!10

Which is to say, only if it is different than what's already there.

Trusted azure

See merge request osdu/platform/ci-cd-pipelines!9

Resolve "Update Snapshots during Maven Builds"

Closes #7

See merge request osdu/platform/ci-cd-pipelines!8

Legal GCP Integration Test

See merge request osdu/platform/ci-cd-pipelines!7