Adding missing environment variables!

33 jobs for darshanaherath-master-patch-95831 in 58 seconds (queued for 4 seconds)
Child pipeline (parent)
Status Name Job ID Coverage
  Azure
failed Delivery API CI-CD v1.0 -- azure #30915
docker-runner

00:00:12

failed Entitlement API CI-CD v1.1 -- azure #30908
docker-runner

00:00:12

failed Legal API CI-CD v2.2 -- azure #30905
docker-runner

00:00:11

failed Search API CI-CD v1.7 -- azure #30911
docker-runner

00:00:13

failed Seismic CI-CD v1.5 -- azure #30912
docker-runner

00:00:13

failed Storage API CI-CD v1.11 -- azure #30910
docker-runner

00:00:12

failed Trajectory CI-CD v1.3.3 -- azure #30914
docker-runner

00:00:12

failed Wellbore CI-CD v1.8.3 -- azure #30906
docker-runner

00:00:14

failed WellboreMarker CI-CD v1.3 -- azure #30909
docker-runner

00:00:13

failed Well CI-CD v2.6 -- azure #30913
docker-runner

00:00:12

failed WellLog CI-CD v1.3.3 -- azure #30907
docker-runner

00:00:13

 
  Aws
failed Delivery API CI-CD v1.0 -- aws #30926
docker-runner

00:00:15

failed Entitlement API CI-CD v1.1 -- aws #30919
docker-runner

00:00:13

failed Legal API CI-CD v2.2 -- aws #30916
docker-runner

00:00:13

failed Search API CI-CD v1.7 -- aws #30922
docker-runner

00:00:13

failed Seismic CI-CD v1.5 -- aws #30923
docker-runner

00:00:16

failed Storage API CI-CD v1.11 -- aws #30921
docker-runner

00:00:14

failed Trajectory CI-CD v1.3.3 -- aws #30925
docker-runner

00:00:16

failed Wellbore CI-CD v1.8.3 -- aws #30917
docker-runner

00:00:15

failed WellboreMarker CI-CD v1.3 -- aws #30920
docker-runner

00:00:16

failed Well CI-CD v2.6 -- aws #30924
docker-runner

00:00:16

failed WellLog CI-CD v1.3.3 -- aws #30918
docker-runner

00:00:13

 
  Gcp
failed Delivery API CI-CD v1.0 -- gcp #30937
docker-runner

00:00:09

failed Entitlement API CI-CD v1.1 -- gcp #30930
docker-runner

00:00:14

failed Legal API CI-CD v2.2 -- gcp #30927
docker-runner

00:00:14

failed Search API CI-CD v1.7 -- gcp #30933
docker-runner

00:00:10

failed Seismic CI-CD v1.5 -- gcp #30934
docker-runner

00:00:10

failed Storage API CI-CD v1.11 -- gcp #30932
docker-runner

00:00:11

failed Trajectory CI-CD v1.3.3 -- gcp #30936
docker-runner

00:00:10

failed Wellbore CI-CD v1.8.3 -- gcp #30928
docker-runner

00:00:14

failed WellboreMarker CI-CD v1.3 -- gcp #30931
docker-runner

00:00:13

failed Well CI-CD v2.6 -- gcp #30935
docker-runner

00:00:10

failed WellLog CI-CD v1.3.3 -- gcp #30929
docker-runner

00:00:14

 
Name Stage Failure
failed
Delivery API CI-CD v1.0 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- gcp Gcp
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- aws Aws
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- azure Azure
secrets. That's bad, so I stopped the pipeline without trying to help you diagnose -- there's too much risk debugging
information would reveal secret values in this job output, which is public.

If your configuration looks good, check out the generate-pipeline.py file. It generates the pipeline matrix that runs
all the jobs (including outputting this message). The first stage of the parent pipeline generated a new pipeline configuration,
which it then executed as a child. Look at the output and see if any recent changes to the generate-pipeline.py script
broke the logic that handles the secrets.
$ test -f "$TEST_COLLECTION_CONFIG"
ERROR: Job failed: exit code 1