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

Bind CI includes to v0.2.0

13 jobs for v0.2.0 in 89 minutes and 41 seconds (queued for 1 second)
latest
Status Name Job ID Coverage
  Build
passed compile-and-unit-test #12951
docker-runner

00:18:00

 
  Containerize
passed aws-containerize #12952
docker-runner

00:11:56

passed azure_containerize #12953
docker-runner

00:23:55

 
  Scan
passed fossa-analyze #12954
docker-runner

00:23:41

 
  Deploy
passed aws-update-ecs #12955
docker-runner

00:05:52

passed azure_config #12957

00:07:44

passed azure_deploy #12956
docker-runner

00:09:58

passed ibm-deploy #12958
docker-runner

00:09:56

 
  Integration
passed aws-test #12959
aws-internal-test

00:03:05

failed azure_test #12960
docker-runner

00:21:45

passed ibm-test #12961
docker-runner

00:29:53

 
  Attribution
skipped fossa-check-notice #12962
docker-runner
skipped fossa-report #12963
docker-runner
 
Name Stage Failure
failed
azure_test Integration
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Running after_script
Uploading artifacts for failed job
ERROR: Job failed: exit code 1