seach-fix-ibm-dipika

69 jobs for search-fix-ibm-dipika in 15 minutes and 18 seconds (queued for 5 seconds)
Child pipeline (parent)
Status Name Job ID Coverage
  Aws
failed Compliance_Legal API CI-CD v2.2 -- aws #668261
osdu-small

00:13:38

failed CRSCatalog API CI-CD v1.0 -- aws #668257
osdu-small

00:13:23

failed CRS Conversion API CI-CD v1.0 -- aws #668254
osdu-small

00:13:32

failed CSVWorkflow__CI-CD_v1.0 -- aws #668265
osdu-small

00:13:20

failed Entitlement API CI-CD v2.0 -- aws #668263
osdu-small

00:13:21

failed R3 Full manifest-based ingestion -- aws #668252
osdu-small

00:12:03

failed Schema API CI-CD v1.0 -- aws #668251
osdu-small

00:01:12

failed Search API R3 CI-CD v1.0 -- aws #668260
osdu-small

00:13:44

failed Storage API CI-CD v1.11 -- aws #668267
osdu-small

00:12:26

failed Trajectory R3 CI-CD v1.0 -- aws #668256
osdu-small

00:12:45

failed Unit CI-CD v1.0 -- aws #668262
osdu-small

00:13:35

failed Wellbore DDMS CI-CD v3.0 -- aws #668253
osdu-small

00:13:12

failed WellboreMarker R3 CI-CD v1.0 -- aws #668264
osdu-small

00:13:32

failed Wellbore R3 CI-CD v1.0 -- aws #668266
osdu-small

00:13:03

failed WellLog R3 CI-CD v1.0 -- aws #668255
osdu-small

00:13:34

failed Well R3 CI-CD v1.0 -- aws #668258
osdu-small

00:13:40

failed Workflow__CI-CD_v1.0 -- aws #668259
osdu-small

00:13:33

 
  Ibm
failed Compliance_Legal API CI-CD v2.2 -- ibm #668278
osdu-small

00:12:47

failed CRSCatalog API CI-CD v1.0 -- ibm #668274
osdu-small

00:13:35

failed CRS Conversion API CI-CD v1.0 -- ibm #668271
osdu-small

00:13:43

failed CSVWorkflow__CI-CD_v1.0 -- ibm #668282
osdu-small

00:13:39

failed Entitlement API CI-CD v2.0 -- ibm #668280
osdu-small

00:12:44

failed R3 Full manifest-based ingestion -- ibm #668269
osdu-small

00:13:19

failed Schema API CI-CD v1.0 -- ibm #668268
osdu-small

00:13:48

failed Search API R3 CI-CD v1.0 -- ibm #668277
osdu-small

00:13:22

failed Storage API CI-CD v1.11 -- ibm #668284
osdu-small

00:13:19

failed Trajectory R3 CI-CD v1.0 -- ibm #668273
osdu-small

00:12:34

failed Unit CI-CD v1.0 -- ibm #668279
osdu-small

00:13:35

failed Wellbore DDMS CI-CD v3.0 -- ibm #668270
osdu-small

00:13:25

failed WellboreMarker R3 CI-CD v1.0 -- ibm #668281
osdu-small

00:13:29

failed Wellbore R3 CI-CD v1.0 -- ibm #668283
osdu-small

00:13:35

failed WellLog R3 CI-CD v1.0 -- ibm #668272
osdu-small

00:13:41

failed Well R3 CI-CD v1.0 -- ibm #668275
osdu-small

00:12:04

failed Workflow__CI-CD_v1.0 -- ibm #668276
osdu-small

00:13:25

 
  Azure
failed Compliance_Legal API CI-CD v2.2 -- azure #668295
osdu-small

00:13:38

failed CRSCatalog API CI-CD v1.0 -- azure #668291
osdu-small

00:13:22

failed CRS Conversion API CI-CD v1.0 -- azure #668288
osdu-small

00:11:21

failed CSVWorkflow__CI-CD_v1.0 -- azure #668299
osdu-small

00:13:24

failed Entitlement API CI-CD v2.0 -- azure #668297
osdu-small

00:13:25

failed R3 Full manifest-based ingestion -- azure #668286
osdu-small

00:13:29

failed Schema API CI-CD v1.0 -- azure #668285
osdu-small

00:13:12

failed Search API R3 CI-CD v1.0 -- azure #668294
osdu-small

00:13:14

failed Storage API CI-CD v1.11 -- azure #668301
osdu-small

00:04:42

failed Trajectory R3 CI-CD v1.0 -- azure #668290
osdu-small

00:12:44

failed Unit CI-CD v1.0 -- azure #668296
osdu-small

00:13:23

failed Wellbore DDMS CI-CD v3.0 -- azure #668287
osdu-small

00:13:15

failed WellboreMarker R3 CI-CD v1.0 -- azure #668298
osdu-small

00:13:32

failed Wellbore R3 CI-CD v1.0 -- azure #668300
osdu-small

00:13:37

failed WellLog R3 CI-CD v1.0 -- azure #668289
osdu-small

00:13:12

failed Well R3 CI-CD v1.0 -- azure #668292
osdu-small

00:13:38

failed Workflow__CI-CD_v1.0 -- azure #668293
osdu-small

00:13:34

 
  Gcp
failed Compliance_Legal API CI-CD v2.2 -- gcp #668312
osdu-small

00:13:17

failed CRSCatalog API CI-CD v1.0 -- gcp #668308
osdu-small

00:13:23

failed CRS Conversion API CI-CD v1.0 -- gcp #668305
osdu-small

00:13:18

failed CSVWorkflow__CI-CD_v1.0 -- gcp #668316
osdu-small

00:13:34

failed Entitlement API CI-CD v2.0 -- gcp #668314
osdu-small

00:13:43

failed R3 Full manifest-based ingestion -- gcp #668303
osdu-small

00:13:40

failed Schema API CI-CD v1.0 -- gcp #668302
osdu-small

00:13:26

failed Search API R3 CI-CD v1.0 -- gcp #668311
osdu-small

00:13:23

failed Storage API CI-CD v1.11 -- gcp #668318
osdu-small

00:13:04

failed Trajectory R3 CI-CD v1.0 -- gcp #668307
osdu-small

00:13:34

failed Unit CI-CD v1.0 -- gcp #668313
osdu-small

00:12:47

failed Wellbore DDMS CI-CD v3.0 -- gcp #668304
osdu-small

00:13:42

failed WellboreMarker R3 CI-CD v1.0 -- gcp #668315
osdu-small

00:12:51

failed Wellbore R3 CI-CD v1.0 -- gcp #668317
osdu-small

00:13:35

failed WellLog R3 CI-CD v1.0 -- gcp #668306
osdu-small

00:12:50

failed Well R3 CI-CD v1.0 -- gcp #668309
osdu-small

00:13:40

failed Workflow__CI-CD_v1.0 -- gcp #668310
osdu-small

00:13:23

 
  Summarize
failed summarize #668319
osdu-small

00:01:27

 
Name Stage Failure
failed
summarize Summarize
Requirement already satisfied: Jinja2<3,>=2.9.0 in ./venv/lib/python3.10/site-packages (from pybadges==2.2.1->-r requirements.txt (line 10)) (2.11.3)
Requirement already satisfied: et-xmlfile in ./venv/lib/python3.10/site-packages (from openpyxl~=3.0.7->-r requirements.txt (line 12)) (1.1.0)
Requirement already satisfied: MarkupSafe>=0.23 in ./venv/lib/python3.10/site-packages (from Jinja2<3,>=2.9.0->pybadges==2.2.1->-r requirements.txt (line 10)) (2.0.1)
WARNING: You are using pip version 21.2.3; however, version 21.3 is available.
You should consider upgrading via the '/builds/osdu/platform/testing/venv/bin/python -m pip install --upgrade pip' command.
$ cd public
/bin/bash: line 227: cd: public: No such file or directory
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Schema API CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v2.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore DDMS CI-CD v3.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Well R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Search API R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
R3 Full manifest-based ingestion -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRS Conversion API CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Compliance_Legal API CI-CD v2.2 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellLog R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Well R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CSVWorkflow__CI-CD_v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Well R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CSVWorkflow__CI-CD_v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Trajectory R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Workflow__CI-CD_v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Compliance_Legal API CI-CD v2.2 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Unit CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRSCatalog API CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellboreMarker R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Unit CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellLog R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellboreMarker R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Workflow__CI-CD_v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
R3 Full manifest-based ingestion -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellboreMarker R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRS Conversion API CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Schema API CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v2.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Workflow__CI-CD_v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CSVWorkflow__CI-CD_v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRSCatalog API CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Search API R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Unit CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Workflow__CI-CD_v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore DDMS CI-CD v3.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRSCatalog API CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Search API R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRSCatalog API CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Compliance_Legal API CI-CD v2.2 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRS Conversion API CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v2.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CSVWorkflow__CI-CD_v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
R3 Full manifest-based ingestion -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore DDMS CI-CD v3.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Search API R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellLog R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Schema API CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore DDMS CI-CD v3.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Wellbore R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellboreMarker R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
WellLog R3 CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Unit CI-CD v1.0 -- gcp Gcp
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Compliance_Legal API CI-CD v2.2 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Trajectory R3 CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Entitlement API CI-CD v2.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Trajectory R3 CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Trajectory R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Well R3 CI-CD v1.0 -- ibm Ibm
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
R3 Full manifest-based ingestion -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
CRS Conversion API CI-CD v1.0 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Storage API CI-CD v1.11 -- azure Azure
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
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Schema API CI-CD v1.0 -- aws Aws
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
Cleaning up file based variables
ERROR: Job failed: exit code 1