Skip to content
Release to staging

Fix #631: Ability to configure data sources when defining data agreement #278

Sign in to view logs

Fix #631: Ability to configure data sources when defining data agreement

Fix #631: Ability to configure data sources when defining data agreement #278

Triggered via push September 25, 2024 09:24
@georgepadayattigeorgepadayatti
pushed 7ffe1b5
main
Status Failure
Total duration 26s
Artifacts –

staging.yaml

on: push
Setup, Build, Publish, and Deploy
16s
Setup, Build, Publish, and Deploy
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Setup, Build, Publish, and Deploy
Setup, Build, Publish, and Deploy
clone of 'https://github.com/decentralised-dataexchange/bb-consent-api-config.git' into submodule path '/home/runner/work/bb-consent-api/bb-consent-api/resources/config' failed
Setup, Build, Publish, and Deploy
Setup, Build, Publish, and Deploy
clone of 'https://github.com/decentralised-dataexchange/bb-consent-api-config.git' into submodule path '/home/runner/work/bb-consent-api/bb-consent-api/resources/config' failed
Setup, Build, Publish, and Deploy
The process '/usr/bin/git' failed with exit code 1
Setup, Build, Publish, and Deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Setup, Build, Publish, and Deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/