Skip to content

issues/181: Added retry logic for Harmony jobs that fail with 5xx errors #637

issues/181: Added retry logic for Harmony jobs that fail with 5xx errors

issues/181: Added retry logic for Harmony jobs that fail with 5xx errors #637

Triggered via push June 4, 2026 18:42
Status Success
Total duration 3m 42s
Artifacts 2
Build python and tf module
2m 9s
Build python and tf module
Build & Publish Docker Image
1m 27s
Build & Publish Docker Image
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build python and tf module
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, getsentry/action-github-app-token@v3, hashicorp/setup-terraform@v3, mamba-org/setup-micromamba@v2, sonarsource/sonarqube-scan-action@v6. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build & Publish Docker Image
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/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
bignbit-0.8.0a8+7593ed3-cumulus-tf
9.34 KB
sha256:4c339fa27e5759009ab281c8ef4340a9701c6254bd02fa6abb4b40359dc18d01
bignbit-dist
697 KB
sha256:10ec89451d5d05424fac1b42eafe032262520b8a8fbc92e4d803fe04f598b3c2