Skip to content

read HEAD tag and apply in docker/metadata-action #285

read HEAD tag and apply in docker/metadata-action

read HEAD tag and apply in docker/metadata-action #285

Triggered via push September 4, 2024 19:37
Status Success
Total duration 2m 2s
Artifacts 2

rust.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

22 warnings
Build, test (x86)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build, test (x86)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build, test (x86)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build, test (x86)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build, test (x86)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build, test (x86)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build, test (x86)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Build, test (x86)
`databricks_kube` (lib test) generated 2 warnings (2 duplicates)
Build, test (x86): databricks-kube/src/crds/databricks_secret.rs#L41
associated functions `controller`, `source_secrets`, `sync_secrets`, `delete_secrets`, and `reconcile` are never used
Build, test (x86): databricks-kube/src/traits/remote_api_resource.rs#L256
associated items `controller` and `self_url_unchecked` are never used
Build, test (x86): databricks-kube/src/traits/remote_api_status.rs#L81
associated function `status_controller` is never used
Build, test (x86)
`databricks_kube` (bin "crd_gen" test) generated 5 warnings (3 duplicates)
Build, test (x86)
`databricks_kube` (bin "databricks_kube" test) generated 5 warnings (5 duplicates)
Build, test (x86)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Build, test (x86)
`databricks_kube` (lib) generated 2 warnings
Build, test (x86): databricks-kube/src/traits/remote_api_resource.rs#L256
associated items `controller` and `self_url_unchecked` are never used
Build, test (x86): databricks-kube/src/traits/remote_api_status.rs#L81
associated function `status_controller` is never used
Build, test (x86)
`databricks_kube` (bin "crd_gen") generated 5 warnings (2 duplicates)

Artifacts

Produced during runtime
Name Size
crd_gen Expired
777 KB
databricks_kube Expired
7.51 MB