generate-all #6117
fybJenkinsgenerate-all.yml
on: schedule
Prerequisite for Generation
3s
generate-bmcapi
/
Generate pnap_bmc_api
25s
generate-ranchersolutionapi
/
Generate pnap_rancher_solution_api
26s
generate-networkapi
/
Generate pnap_network_api
21s
generate-ipapi
/
Generate pnap_ip_api
24s
generate-auditapi
/
Generate pnap_audit_api
20s
generate-tagapi
/
Generate pnap_tag_api
23s
generate-networkstorageapi
/
Generate pnap_network_storage_api
22s
generate-locationapi
/
Generate pnap_location_api
27s
generate-invoicingapi
/
Generate pnap_invoicing_api
16s
generate-paymentsapi
/
Generate pnap_payments_api
19s
Matrix: validate-all / run-generic-tests / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-auditapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-bmcapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-invoicingapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-ipapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-locationapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-networkapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-networkstorageapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-paymentsapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-rancherapi / test / test
Waiting for pending jobs
Matrix: validate-all / build-and-test-tagapi / test / test
Waiting for pending jobs
validate-all
/
Publish Test Results
Annotations
11 warnings
|
generate-invoicingapi / Generate pnap_invoicing_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-networkstorageapi / Generate pnap_network_storage_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-tagapi / Generate pnap_tag_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-bmcapi / Generate pnap_bmc_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-ranchersolutionapi / Generate pnap_rancher_solution_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-locationapi / Generate pnap_location_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-networkapi / Generate pnap_network_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-paymentsapi / Generate pnap_payments_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-ipapi / Generate pnap_ip_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
generate-auditapi / Generate pnap_audit_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2, actions/upload-artifact@v4. 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/
|
|
Push Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4. 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 | |
|---|---|---|---|
|
pnap_audit_api
|
35.9 KB |
sha256:bfdb369abcdefb4fbf2d267adb4700ae054e360e2a027a2e5b182b0ada34c000
|
|
|
pnap_bmc_api
|
196 KB |
sha256:b210b80b8304fbbe837a8bc15366dd2e4f9c4fdc46040dfae73e181f86bf1478
|
|
|
pnap_invoicing_api
|
38.7 KB |
sha256:2836175e4a8c30ee39a6494ce3544b6210d1a53a1a43847e9767ba22b565d4f9
|
|
|
pnap_ip_api
|
50.3 KB |
sha256:c6d49463dd87736c3a5cf5cb8365a4dd2b820cecfc0d3b3291e16c350dcc1024
|
|
|
pnap_location_api
|
34.1 KB |
sha256:939c43e10750bd752e19c7d3f8d7df8f9635d9b583c295b2581e6aa3e5e56839
|
|
|
pnap_network_api
|
98.9 KB |
sha256:64669601a6295af1c00dcbbe8c7f75467a7a79a791a9384a5c74df40fee2cc98
|
|
|
pnap_network_storage_api
|
77.5 KB |
sha256:07c816197d9046f6dbce1339d37ea353457f8e1fbcf8516732f8cf14ed9f9eef
|
|
|
pnap_payments_api
|
41.9 KB |
sha256:0e21ce96ae8ad4b50cc6bda76d8ddfedb2a44fe183e56728d4dc58ba14415ebe
|
|
|
pnap_rancher_solution_api
|
60 KB |
sha256:5630829195f79068e3e378a0fe88714b40257b18d5505c193ad8da5c3866e4b2
|
|
|
pnap_tag_api
|
46 KB |
sha256:13b80d08ed55bde44cc43e6978a6eca3b6e70db5ac19879b3be43f1d38c27f29
|
|