Update R3 Testing/A00_Environment/.gitkeep, R3...

Update R3 Testing/A00_Environment/.gitkeep, R3 Testing/D01_WellDataWorkflow/.gitkeep, R3 Testing/D02_WellboreWorkflow/.gitkeep, R3 Testing/A01_ComplianceAPI/.gitkeep files
48 jobs for Gwenola.Michaud-master-patch-51143 in 1 minute and 53 seconds (queued for 9 seconds)
Child pipeline (parent)
Status Name Job ID Coverage
  Azure
failed Delivery API CI-CD v1.0 -- azure #65571
docker-runner

00:00:18

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

00:00:19

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

00:00:18

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

00:00:23

failed Security CI-CD v0.1 -- azure #65565
docker-runner

00:00:23

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

00:00:22

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

00:00:21

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

00:00:20

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

00:00:19

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

00:00:21

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

00:00:21

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

00:00:21

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

00:00:20

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

00:00:21

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

00:00:19

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

00:00:21

failed Security CI-CD v0.1 -- ibm #65577
docker-runner

00:00:21

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

00:00:21

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

00:00:22

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

00:00:19

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

00:00:20

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

00:00:19

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

00:00:23

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

00:00:21

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

00:00:21

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

00:00:21

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

00:00:22

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

00:00:23

failed Security CI-CD v0.1 -- aws #65589
docker-runner

00:00:21

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

00:00:22

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

00:00:22

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

00:00:23

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

00:00:21

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

00:00:22

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

00:00:21

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

00:00:19

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

00:00:15

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

00:00:20

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

00:00:22

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

00:00:18

failed Security CI-CD v0.1 -- gcp #65601
docker-runner

00:00:21

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

00:00:17

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

00:00:19

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

00:00:17

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

00:00:22

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

00:00:18

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

00:00:18

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

00:00:21

 
Name Stage Failure
failed
Trajectory CI-CD v1.3.3 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Security CI-CD v0.1 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Security CI-CD v0.1 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Security CI-CD v0.1 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- gcp Gcp
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Trajectory CI-CD v1.3.3 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Legal API CI-CD v2.2 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- aws Aws
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Delivery API CI-CD v1.0 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellboreMarker CI-CD v1.3 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
WellLog CI-CD v1.3.3 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- ibm Ibm
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Search API CI-CD v1.7 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Well CI-CD v2.6 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Seismic CI-CD v1.5 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Security CI-CD v0.1 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v1.1 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1
failed
Wellbore CI-CD v1.8.3 -- azure Azure
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"
Uploading artifacts for failed job
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1