Skip to content

Remote Trigger Registration Checks #29003

Remote Trigger Registration Checks

Remote Trigger Registration Checks #29003

Triggered via pull request May 7, 2026 13:32
Status Success
Total duration 11m 1s
Artifacts

docker-build.yml

on: pull_request
docker-ccip-plugins  /  init
8s
docker-ccip-plugins / init
docker-ccip  /  init
9s
docker-ccip / init
docker-core-plugins-testing  /  init
6s
docker-core-plugins-testing / init
docker-core-plugins  /  init
6s
docker-core-plugins / init
docker-core  /  init
6s
docker-core / init
docker-ccip-plugins  /  set-build-matrix
3s
docker-ccip-plugins / set-build-matrix
docker-ccip  /  set-build-matrix
3s
docker-ccip / set-build-matrix
docker-core-plugins-testing  /  set-build-matrix
2s
docker-core-plugins-testing / set-build-matrix
docker-core-plugins  /  set-build-matrix
3s
docker-core-plugins / set-build-matrix
docker-core  /  set-build-matrix
4s
docker-core / set-build-matrix
Matrix: docker-ccip-plugins / build-publish
Matrix: docker-ccip / build-publish
Matrix: docker-core-plugins-testing / build-publish
Matrix: docker-core-plugins / build-publish
Matrix: docker-core / build-publish
docker-ccip-plugins  /  docker-manifest
23s
docker-ccip-plugins / docker-manifest
docker-ccip  /  docker-manifest
26s
docker-ccip / docker-manifest
docker-core-plugins-testing  /  docker-manifest
23s
docker-core-plugins-testing / docker-manifest
docker-core-plugins  /  docker-manifest
36s
docker-core-plugins / docker-manifest
docker-core  /  docker-manifest
24s
docker-core / docker-manifest
deploy-nightly-ccip
0s
deploy-nightly-ccip
call-post-docker-build  /  ...  /  changes
call-post-docker-build / call-cre-local-env-tests / changes
call-post-docker-build  /  ...  /  CRE Resource Regression Test
call-post-docker-build / call-cre-resource-regression-tests / CRE Resource Regression Test
deploy-nightly-core
0s
deploy-nightly-core
call-post-docker-build  /  ...  /  Build Information
call-post-docker-build / call-legacy-non-functional-tests / Build Information
call-post-docker-build  /  ...  /  Build Information
call-post-docker-build / call-legacy-system-tests / Build Information
Matrix: call-post-docker-build / call-legacy-non-functional-tests / test-nightly
Waiting for pending jobs
Matrix: call-post-docker-build / call-legacy-system-tests / test-nightly
Waiting for pending jobs
call-post-docker-build  /  ...  /  test-cli
call-post-docker-build / call-cre-local-env-tests / test-cli
call-post-docker-build  /  ...  /  Notify about test Failure
call-post-docker-build / call-cre-resource-regression-tests / Notify about test Failure
call-post-docker-build  /  ...  /  Notify about local env startup failure
call-post-docker-build / call-cre-local-env-tests / Notify about local env startup failure
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
docker-ccip / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-ccip-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core-plugins-testing / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-ccip-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-ccip / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core-plugins-testing / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
docker-core-plugins-testing / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
docker-core-plugins-testing / docker-manifest
Skip output 'name' since it may contain secret.
docker-ccip / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
docker-ccip / docker-manifest
Skip output 'name' since it may contain secret.
docker-ccip-plugins / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
docker-ccip-plugins / docker-manifest
Skip output 'name' since it may contain secret.
docker-core / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
docker-core / docker-manifest
Skip output 'name' since it may contain secret.
docker-core-plugins / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
docker-core-plugins / docker-manifest
Skip output 'name' since it may contain secret.