Skip to content

Enhance per bucket, and per document monitor notification message ctx… #17

Enhance per bucket, and per document monitor notification message ctx…

Enhance per bucket, and per document monitor notification message ctx… #17

Triggered via push March 21, 2024 21:30
Status Failure
Total duration 21m 49s
Artifacts
Get-CI-Image-Tag  /  Get-CI-Image-Tag
5s
Get-CI-Image-Tag / Get-CI-Image-Tag
Matrix: Build and test Alerting
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Build and test Alerting (17)
Process completed with exit code 1.
Get-CI-Image-Tag / Get-CI-Image-Tag
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build and test Alerting (11)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-java@v1, actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build and test Alerting (11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build and test Alerting (11)
Docker pull failed with exit code 1, back off 2.131 seconds before retry.
Build and test Alerting (17)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-java@v1, actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build and test Alerting (17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/