Updated config in CLI e2e Pipeline for nodepool and integration used #5017
agrasthAnnotations
9 errors and 6 warnings
|
pip ubuntu
Canceling since a higher priority waiting request for Python Tests-3391-refs/heads/master exists
|
|
pip ubuntu
The operation was canceled.
|
|
pipenv ubuntu
Canceling since a higher priority waiting request for Python Tests-3391-refs/heads/master exists
|
|
pipenv ubuntu
The operation was canceled.
|
|
pipenv windows
Canceling since a higher priority waiting request for Python Tests-3391-refs/heads/master exists
|
|
pipenv windows
The operation was canceled.
|
|
pip windows
Canceling since a higher priority waiting request for Python Tests-3391-refs/heads/master exists
|
|
pip windows
The operation was canceled.
|
|
Python Tests
Canceling since a higher priority waiting request for Python Tests-3391-refs/heads/master exists
|
|
pipenv macos
JGC-413 - Skip until artifactory bootstrap in osx is fixed
|
|
pip macos
JGC-413 - Skip until artifactory bootstrap in osx is fixed
|
|
pip ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, jfrog-fastci/fastci@v0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
pipenv ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, jfrog-fastci/fastci@v0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
pipenv windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, jfrog-fastci/fastci@v0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
pip windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, jfrog-fastci/fastci@v0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|