Partition Service: Updated health check URL & related test cases

109 jobs for partition_test_case_fix in 6 minutes and 7 seconds (queued for 10 seconds)
Child pipeline (parent)
Status Name Job ID Coverage
  Aws
failed Compliance_Legal API CI-CD v2.2 -- aws #496015
osdu-small

00:04:14

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

00:04:27

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

00:03:57

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

00:04:54

failed Dataset API CI-CD v1.0 -- aws #496004
osdu-small

00:04:28

failed Entitlement API CI-CD v1.1 -- aws #496019
osdu-small

00:04:05

failed File API CI-CD v1.0 -- aws #496014
osdu-small

00:05:05

failed Indexer API CI-CD v1.0 -- aws #496017
osdu-small

00:05:04

failed OpenVDS CI-CD v1.0 -- aws #496020
osdu-small

00:04:13

failed Partition API CI-CD v1.0 -- aws #496026
osdu-small

00:04:58

failed R3_Ingestion CI-CD 2021-02-09 -- aws #496002
osdu-small

00:03:41

failed Registration API CI-CD v1.0 -- aws #496016
osdu-small

00:04:33

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

00:02:40

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

00:04:03

failed Security CI-CD v0.1 -- aws #496008
osdu-small

00:04:42

failed Security_testcases CI-CD v1.0 -- aws #496007
osdu-small

00:04:15

failed SeismicDMS_API_CI-CD_v1.0 -- aws #496024
osdu-small

00:04:11

failed Seismic R3 CI-CD v1.0 -- aws #496027
osdu-small

00:03:57

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

00:04:29

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

00:04:27

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

00:04:28

failed Wellbore DDMS CI-CD v1.2 -- aws #496003
osdu-small

00:03:52

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

00:04:43

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

00:03:48

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

00:04:00

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

00:04:14

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

00:04:32

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

00:04:41

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

00:05:04

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

00:05:05

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

00:04:39

failed Dataset API CI-CD v1.0 -- ibm #496031
osdu-small

00:04:41

failed Entitlement API CI-CD v1.1 -- ibm #496046
osdu-small

00:04:38

failed File API CI-CD v1.0 -- ibm #496041
osdu-small

00:04:14

failed Indexer API CI-CD v1.0 -- ibm #496044
osdu-small

00:03:49

failed OpenVDS CI-CD v1.0 -- ibm #496047
osdu-small

00:04:19

failed Partition API CI-CD v1.0 -- ibm #496053
osdu-small

00:04:29

failed R3_Ingestion CI-CD 2021-02-09 -- ibm #496029
osdu-small

00:04:27

failed Registration API CI-CD v1.0 -- ibm #496043
osdu-small

00:05:05

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

00:04:42

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

00:04:30

failed Security CI-CD v0.1 -- ibm #496035
osdu-small

00:04:27

failed Security_testcases CI-CD v1.0 -- ibm #496034
osdu-small

00:04:09

failed SeismicDMS_API_CI-CD_v1.0 -- ibm #496051
osdu-small

00:03:51

failed Seismic R3 CI-CD v1.0 -- ibm #496054
osdu-small

00:05:03

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

00:04:39

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

00:04:31

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

00:04:43

failed Wellbore DDMS CI-CD v1.2 -- ibm #496030
osdu-small

00:04:29

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

00:04:28

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

00:04:21

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

00:04:11

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

00:04:11

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

00:03:44

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

00:04:35

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

00:04:59

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

00:04:32

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

00:04:07

failed Dataset API CI-CD v1.0 -- azure #496058
osdu-small

00:04:37

failed Entitlement API CI-CD v1.1 -- azure #496073
osdu-small

00:04:24

failed File API CI-CD v1.0 -- azure #496068
osdu-small

00:04:44

failed Indexer API CI-CD v1.0 -- azure #496071
osdu-small

00:04:20

failed OpenVDS CI-CD v1.0 -- azure #496074
osdu-small

00:04:31

failed Partition API CI-CD v1.0 -- azure #496080
osdu-small

00:04:13

failed R3_Ingestion CI-CD 2021-02-09 -- azure #496056
osdu-small

00:04:26

failed Registration API CI-CD v1.0 -- azure #496070
osdu-small

00:05:03

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

00:04:34

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

00:04:24

failed Security CI-CD v0.1 -- azure #496062
osdu-small

00:05:03

failed Security_testcases CI-CD v1.0 -- azure #496061
osdu-small

00:04:36

failed SeismicDMS_API_CI-CD_v1.0 -- azure #496078
osdu-small

00:04:29

failed Seismic R3 CI-CD v1.0 -- azure #496081
osdu-small

00:04:21

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

00:04:35

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

00:04:38

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

00:04:28

failed Wellbore DDMS CI-CD v1.2 -- azure #496057
osdu-small

00:04:31

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

00:05:03

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

00:04:33

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

00:04:27

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

00:04:25

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

00:04:23

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

00:04:37

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

00:04:07

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

00:05:00

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

00:04:29

failed Dataset API CI-CD v1.0 -- gcp #496085
osdu-small

00:04:30

failed Entitlement API CI-CD v1.1 -- gcp #496100
osdu-small

00:04:29

failed File API CI-CD v1.0 -- gcp #496095
osdu-small

00:04:28

failed Indexer API CI-CD v1.0 -- gcp #496098
osdu-small

00:04:18

failed OpenVDS CI-CD v1.0 -- gcp #496101
osdu-small

00:04:51

failed Partition API CI-CD v1.0 -- gcp #496107
osdu-small

00:04:47

failed R3_Ingestion CI-CD 2021-02-09 -- gcp #496083
osdu-small

00:04:27

failed Registration API CI-CD v1.0 -- gcp #496097
osdu-small

00:05:03

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

00:05:01

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

00:04:30

failed Security CI-CD v0.1 -- gcp #496089
osdu-small

00:04:23

failed Security_testcases CI-CD v1.0 -- gcp #496088
osdu-small

00:04:24

failed SeismicDMS_API_CI-CD_v1.0 -- gcp #496105
osdu-small

00:04:58

failed Seismic R3 CI-CD v1.0 -- gcp #496108
osdu-small

00:05:02

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

00:04:54

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

00:04:29

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

00:04:28

failed Wellbore DDMS CI-CD v1.2 -- gcp #496084
osdu-small

00:04:28

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

00:04:49

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

00:04:48

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

00:04:29

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

00:04:55

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

00:04:38

 
  Summarize
failed summarize #496109
osdu-small

00:00:50

 
Name Stage Failure
failed
summarize Summarize
Requirement already satisfied: pybadges==2.2.1 in ./venv/lib/python3.9/site-packages (from -r requirements.txt (line 10)) (2.2.1)
Requirement already satisfied: Jinja2<3,>=2.9.0 in ./venv/lib/python3.9/site-packages (from pybadges==2.2.1->-r requirements.txt (line 10)) (2.11.3)
Requirement already satisfied: MarkupSafe>=0.23 in ./venv/lib/python3.9/site-packages (from Jinja2<3,>=2.9.0->pybadges==2.2.1->-r requirements.txt (line 10)) (1.1.1)
WARNING: You are using pip version 21.1.3; however, version 21.2.3 is available.
You should consider upgrading via the '/builds/osdu/platform/testing/venv/bin/python -m pip install --upgrade pip' command.
$ cd public && ../Summarize_Newman_Html_Reports.py
/bin/bash: line 222: cd: public: No such file or directory
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
Seismic 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
Registration 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
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
Registration 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
Registration 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 -- 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
Indexer 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
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
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
OpenVDS 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
Partition 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
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
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
Partition 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
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
File 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
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
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
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
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
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
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
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
Dataset 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
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
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 v1.1 -- 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
Dataset 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
Security_testcases 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
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
Security CI-CD v0.1 -- 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
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
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
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
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
Entitlement API CI-CD v1.1 -- 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
Dataset 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
OpenVDS 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 -- 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
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
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
File 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
Wellbore DDMS CI-CD v1.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
Wellbore DDMS CI-CD v1.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
SeismicDMS_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
R3_Ingestion CI-CD 2021-02-09 -- 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
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
Partition 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
Registration 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
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
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
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
Security_testcases 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 -- 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
Wellbore DDMS CI-CD v1.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
R3_Ingestion CI-CD 2021-02-09 -- 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
Security CI-CD v0.1 -- 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 -- 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 -- 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 v1.1 -- 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
Security CI-CD v0.1 -- 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
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
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
R3_Ingestion CI-CD 2021-02-09 -- 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
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
Seismic 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 -- 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
Security CI-CD v0.1 -- 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
SeismicDMS_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
Seismic 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 -- 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
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
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
File 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
Indexer 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
Indexer 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
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
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
Dataset 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
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
OpenVDS 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
Partition 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
File 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
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
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
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
OpenVDS 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
Security_testcases 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
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
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
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
SeismicDMS_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
Security_testcases 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 v1.1 -- 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
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
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
Seismic 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
SeismicDMS_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
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
Indexer 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
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
Wellbore DDMS CI-CD v1.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
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
R3_Ingestion CI-CD 2021-02-09 -- 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 -- 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