There is a security vulnerability in SSH key-generation using GitKraken < v8.0.1. If you used this tool to create SSH keys, please update GitKraken and regenerate. If you need help with this, contact forum-support@opengroup.org

pointed to ibm-ubi8-java branch

23 jobs for ibm-ubi8-java in 20 minutes and 50 seconds (queued for 4 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #556579
osdu-small allowed to fail

00:00:10

failed deprecated-pipeline-include #556578
allowed to fail

00:00:09

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

00:06:00

 
  Containerize
passed aws-containerize #556584
osdu-medium

00:01:22

passed azure_containerize #556581
osdu-medium

00:01:37

passed osdu-gcp-containerize-gcloud #556582

00:01:45

passed osdu-gcp-containerize-gitlab #556583
osdu-medium

00:00:58

 
  Scan
passed bandit-sast #556587
osdu-medium

00:04:14

passed fossa-analyze #556585
osdu-medium

00:13:06

passed gemnasium-maven-dependency_scanning #556586
osdu-medium

00:05:08

passed license_scanning #556590
osdu-medium

00:05:49

passed semgrep-sast #556588
osdu-medium

00:03:43

passed spotbugs-sast #556589
osdu-large

00:14:04

 
  Deploy
passed aws-update-eks #556593
osdu-medium

00:01:06

passed azure_deploy #556591
osdu-medium

00:00:11

passed ibm-deploy #556594
osdu-medium

00:01:31

passed osdu-gcp-deploy #556592

00:01:03

 
  Integration
passed aws-test-java #556597
osdu-medium

00:03:50

passed azure_test #556595
osdu-medium

00:09:53

passed ibm-test #556598
osdu-medium

00:04:42

passed osdu-gcp-test #556596
osdu-medium

00:04:02

 
  Attribution
failed fossa-check-notice #556599
osdu-small

00:01:21

passed fossa-report #556600
osdu-small

00:01:13

 
Name Stage Failure
failed
fossa-check-notice Attribution
You can download the NOTICE file from this job's artifacts and directly commit it to the repository to resolve
this. Before doing so, review the differences to make sure that they make sense given the changes that you have
made. If they do not, reach out to a maintainer to help diagnose the issue.
Uploading artifacts for failed job
Uploading artifacts...
public: found 2 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=556599 responseStatus=201 Created token=hzAzF_aV
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 2f172789 as ibm-ubi8-java...

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