new topics

8 jobs for users/nikhil/perfRegister in 19 minutes and 28 seconds (queued for 3 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #547796
osdu-small allowed to fail

00:00:06

failed deprecated-gcp-pipeline #547795
allowed to fail

00:00:08

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

00:05:59

 
  Scan
passed bandit-sast #547799
osdu-medium

00:05:11

passed gemnasium-maven-dependency_scanning #547798
osdu-medium

00:04:39

passed license_scanning #547802
osdu-medium

00:05:08

passed semgrep-sast #547800
osdu-medium

00:04:10

passed spotbugs-sast #547801
osdu-large

00:13:19

 
Name Stage Failure
failed
deprecated-gcp-pipeline .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/register/.git/
Checking out 2e0555e9 as users/nikhil/perfRegister...

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The integration test environment previously managed by the cloud-providers/gcp.yml is no longer supported. Consider removing it from your .gitlab-ci.yml
$ /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