fix(autonomy_engine_control): name of message type

5 jobs for 95-add-autonomy-object in 2 minutes (queued for 2 seconds)

View job dependencies in the pipeline graph!

You can now group jobs in the pipeline graph based on which jobs are configured to run first, if you use the needs: keyword to establish job dependencies in your CI/CD pipelines. Learn how to speed up your pipeline with needs.

Provide feedback
Status Job ID Name Coverage
  Lint
passed #1078188
docker
lint

00:00:32

 
  Build
passed #1078189
shell
build

00:00:40

 
  Test
failed #1078190
shell
test

00:00:31

passed #1078191
shell
test-js

00:00:48

 
  Tag Docker
skipped #1078192
shell
tag_docker
 
Name Stage Failure
failed
test Test
soar_flasgger_test    | loading cached ref: https://geojson.org/schema/Point.json
soar_flasgger_test | loading cached ref: https://geojson.org/schema/Polygon.json
soar_flasgger_test | TEST: compiled schema matches openapi v3 spec
soar_flasgger_test exited with code 1
Stopping soar_flasgger_test ...
Stopping soar_flasgger_test ...
done Aborting on container exit...
Running after_script
Uploading artifacts for failed job
ERROR: Job failed: exit status 1

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).