chore: bump Helm chart to appVersion 0.33.0 and trigger release workf… #15
release-helm-chart.yaml
on: push
validate-chart
5s
trigger-deployment-tools-update
14m 59s
Annotations
10 errors, 4 warnings, and 1 notice
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T13:00:22.418Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 13.018790836s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T13:00:04.832Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 17.233751063s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:51.666Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 12.750084099s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:43.016Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 8.314413431s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:40.382Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 2.284056523s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:38.148Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 1.820570226s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:35.888Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 1.915687478s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:33.927Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 1.611582077s
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:32.868Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 723.37222ms
|
|
trigger-deployment-tools-update
failed to run command, retrying
time: "2026-04-16T12:59:32.154Z"
level: ERROR
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
error: "command failed: exit status 1"
retry_in: 364.411521ms
|
|
release-chart / setup
No file matched to [/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/*requirements*.txt,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/*requirements*.in,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/*constraints*.txt,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/*constraints*.in,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/pyproject.toml,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/uv.lock,/home/runner/work/cloudcost-exporter/cloudcost-exporter/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
release-chart / release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-***-token@29824e69f54612133e76f7eaac726eef6c875baf, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, azure/setup-helm@1a275c3b69536ee54be43f2070a358922e12c8d4, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, hashicorp/vault-action@a1b77a09293a4366e48a5067a86692ac6e94fdc0, softprops/action-gh-release@de2c0eb89ae2a093876385947365aca7b0e5f844. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
trigger-deployment-tools-update
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
trigger-deployment-tools-update
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
|
|
trigger-deployment-tools-update
running command
time: "2026-04-16T12:59:31.765Z"
level: INFO
argo_wf_instance: ops
org: grafana
repo: cloudcost-exporter
commit: f64b1ba00f4159dd280deae388f2fbebbb3a91a9
commit_author: simaarfania
build_number: "15"
build_event: push
command: submit
namespace: platform-monitoring-cd
extraArgs:
- --parameter
- chartfile_file=ksonnet/lib/cloudcost-exporter/chartfile.yaml
- --parameter
- chart_name=grafana/cloudcost-exporter
- --parameter
- workflow_name=cloudcost-exporter-gh-runners
- --parameter
- workflow_namespace=platform-monitoring-cd
|