Skip to content

chore: add silo-to-silo turbo deployment (#250) #694

chore: add silo-to-silo turbo deployment (#250)

chore: add silo-to-silo turbo deployment (#250) #694

Triggered via push December 20, 2024 19:37
Status Success
Total duration 2m 0s
Artifacts
Shared  /  Backstage
7s
Shared / Backstage
Matrix: Shared / Static Analysis
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 15 warnings
Shared / Backstage
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (erc20-locker, contract, ethereum, erc20-connector, 1, erc20-connector, 1.18, tru...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (bridge-token-factory-on-near, contract, near, bridge-token-factory, 1, ., 1.18, ...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (silo-to-silo, contract, aurora, silo-to-silo, 1, silo-to-silo, 1.18, true, --fil...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (bridge-token-on-near, contract, near, bridge-token, 1, ., 1.18, false, --filter-...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (bridge-near-token-locker, contract, near, token-locker, 1, ., 1.18, false, --fil...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (erc20-bridge-token, contract, ethereum, erc20-bridge-token, 1, erc20-bridge-toke...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Static Analysis (bridge-common, contract, near, bridge-common, 1, ., 1.18, false, --filter-paths ...
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Shared / Backstage
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version
Shared / Backstage
unable to detect go version