feat: add fetching of kofuvi addresses for br org (#4) #43
Triggered via push
September 10, 2024 11:52
Status
Failure
Total duration
30d 0h 27m 27s
Artifacts
1
build-deploy-workflow.yml
on: push
run
/
build
43s
run
/
...
/
post-deploy-tests
run
/
...
/
post-deploy-tests
run
/
redeploy-staging
0s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
SondreJDigdir
approved
|
staging |
Annotations
1 error and 16 warnings
run / swap-staging-prod
The deployment was rejected or didn't satisfy other protection rules.
|
run / build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L408
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L422
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L530
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L408
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L422
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L530
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L408
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L422
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L530
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L408
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L422
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / build:
src/Dan.Plugin.Tilda/Tilda.cs#L530
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
run / deploy-dev
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
run / deploy-staging
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "dan-plugin-tilda".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
dan-plugin-tilda
Expired
|
24.5 MB |
|