Skip to content

Release Nightly

Release Nightly #5

Triggered via schedule May 2, 2026 00:59
Status Failure
Total duration 1d 0h 0m 32s
Artifacts

release-nightly.yml

on: schedule
Matrix: build-all-in-one-nightly
Matrix: build-app-nightly
Matrix: build-local-nightly
Matrix: build-otel-collector-nightly
Publish All-in-One Nightly Manifest
0s
Publish All-in-One Nightly Manifest
Publish App Nightly Manifest
0s
Publish App Nightly Manifest
Publish Local Nightly Manifest
0s
Publish Local Nightly Manifest
Publish OTel Collector Nightly Manifest
Publish OTel Collector Nightly Manifest
slack-notify-failure
6s
slack-notify-failure
OpenTelemetry Export Trace
8s
OpenTelemetry Export Trace
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
Build OTel Collector Nightly (amd64)
Username and password required
Build OTel Collector Nightly (arm64)
The strategy configuration was canceled because "build-otel-collector-nightly.amd64_linux_amd64_ubuntu-" failed
Build All-in-One Nightly (amd64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build App Nightly (amd64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build Local Nightly (arm64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build All-in-One Nightly (arm64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build App Nightly (arm64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build Local Nightly (amd64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
slack-notify-failure
Specify secrets.SLACK_WEBHOOK_URL
OpenTelemetry Export Trace
[{"code":14,"details":"Name resolution failed for target dns:v1","metadata":{}}]
Build OTel Collector Nightly (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
slack-notify-failure
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 8398a7/action-slack@v3, actions/checkout@v4, actions/github-script@v7. 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/