Multiuser POC

44 jobs for multiuser_poc in 1 minute and 20 seconds (queued for 11 seconds)
Child pipeline (parent)
Status Name Job ID Coverage
  Azure
failed Delivery API CI-CD v1.0 -- azure #91686
docker-runner

00:00:12

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

00:00:26

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

00:00:27

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

00:00:27

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

00:00:27

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

00:00:27

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

00:00:25

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

00:00:27

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

00:00:28

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

00:00:26

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

00:00:26

 
  Ibm
failed Delivery API CI-CD v1.0 -- ibm #91697
docker-runner

00:00:11

failed Entitlement API CI-CD v1.1 -- ibm #91690
docker-runner

00:00:12

failed Legal API CI-CD v2.2 -- ibm #91687
docker-runner

00:00:12

failed Search API CI-CD v1.7 -- ibm #91693
docker-runner

00:00:11

failed Seismic CI-CD v1.5 -- ibm #91694
docker-runner

00:00:11

failed Storage API CI-CD v1.11 -- ibm #91692
docker-runner

00:00:13

failed Trajectory CI-CD v1.3.3 -- ibm #91696
docker-runner

00:00:10

failed Wellbore CI-CD v1.8.3 -- ibm #91688
docker-runner

00:00:11

failed WellboreMarker CI-CD v1.3 -- ibm #91691
docker-runner

00:00:11

failed Well CI-CD v2.6 -- ibm #91695
docker-runner

00:00:11

failed WellLog CI-CD v1.3.3 -- ibm #91689
docker-runner

00:00:12

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

00:00:12

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

00:00:11

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

00:00:10

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

00:00:12

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

00:00:12

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

00:00:11

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

00:00:12

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

00:00:11

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

00:00:12

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

00:00:12

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

00:00:10

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

00:00:08

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

00:00:13

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

00:00:13

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

00:00:12

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

00:00:09

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

00:00:13

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

00:00:07

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

00:00:12

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

00:00:12

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

00:00:08

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

00:00:12

 
Name Stage Failure
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
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
Seismic CI-CD v1.5 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Delivery API CI-CD v1.0 -- ibm Ibm
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
Trajectory CI-CD v1.3.3 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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 -- ibm Ibm
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
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
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
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