Merge branch 'GONRG-3370' into 'master'

CI CD variable for helm package charts was added [GONRG-3370]

See merge request !118
9 jobs for gcp-helm-release-0-1 in 12 minutes and 23 seconds (queued for 2 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #611695
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #611694
allowed to fail

00:00:07

 
  Build
passed compile-and-unit-test #611696
osdu-medium

00:05:33

passed osdu-gcp-helm-charts #611697
osdu-small

00:00:09

 
  Scan
passed bandit-sast #611699
osdu-medium

00:05:18

passed gemnasium-maven-dependency_scanning #611698
osdu-medium

00:06:36

passed license_scanning #611702
osdu-medium

00:06:29

passed semgrep-sast #611700
osdu-medium

00:03:10

failed spotbugs-sast #611701
osdu-large allowed to fail

00:03:29

 
Name Stage Failure
failed
spotbugs-sast Scan
Running after_script
Running after script...
$ tar -cC ~/.m2 repository | tar -xC $CI_PROJECT_DIR/.m2
Uploading artifacts for failed job
Uploading artifacts...
WARNING: gl-sast-report.json: no matching files
ERROR: No files to upload
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
deprecated-pipeline-include .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
Checking out fd28a686 as gcp-helm-release-0-1...

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The FOSSA scanner now supports different build environments, which should be specified directly. Consider using fossa-maven.yml instead.
$ /bin/false
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine:latest with digest alpine@sha256:e1c082e3d3c45cccac829840a25941e679c25d438cc8412c2fa221cf1a824e6a ...
$ echo "$DEPRECATED_MSG"
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1