Skip to content

Create separate agent daemonsets on windows for container insights and application signals #224

Create separate agent daemonsets on windows for container insights and application signals

Create separate agent daemonsets on windows for container insights and application signals #224

Triggered via pull request August 29, 2024 21:30
Status Success
Total duration 35m 22s
Artifacts
HelmChartsIntegrationTest
19m 6s
HelmChartsIntegrationTest
HelmChartsIntegrationTestWindows-2022
34m 48s
HelmChartsIntegrationTestWindows-2022
HelmChartsIntegrationTestWindows-2019
33m 51s
HelmChartsIntegrationTestWindows-2019
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
HelmChartsIntegrationTest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2, nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
HelmChartsIntegrationTestWindows-2019
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2, nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
HelmChartsIntegrationTestWindows-2022
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2, nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/