Skip to content

Added possibility for configuring priorities per service (#436) #1144

Added possibility for configuring priorities per service (#436)

Added possibility for configuring priorities per service (#436) #1144

Triggered via push October 24, 2024 12:50
Status Success
Total duration 15m 49s
Artifacts

resilence.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
resilence_test
The following actions uses node12 which is deprecated and will be forced to run on node16: mikepenz/action-junit-report@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
resilence_test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, gradle/wrapper-validation-action@v1, actions/setup-java@v3, actions/cache@v3, mikepenz/action-junit-report@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
resilence_test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
resilence_test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/