Skip to content

Allow reporting custom increment in telemetry counters (#2296) #641

Allow reporting custom increment in telemetry counters (#2296)

Allow reporting custom increment in telemetry counters (#2296) #641

Triggered via push July 9, 2024 11:28
Status Success
Total duration 23m 53s
Artifacts

release.yml

on: push
Build and push nucliadb docker image
9m 32s
Build and push nucliadb docker image
Deploy Helm chart and trigger internal CI
6s
Deploy Helm chart and trigger internal CI
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build wheels
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, dorny/paths-filter@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and push nucliadb docker image
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/login-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy Helm chart and trigger internal CI
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, azure/setup-helm@v3, peter-evans/repository-dispatch@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/