Skip to content

Mark as not compatible with configuration cache #120

Mark as not compatible with configuration cache

Mark as not compatible with configuration cache #120

Triggered via pull request December 13, 2023 23:03
Status Success
Total duration 2m 39s
Artifacts

nebula.yml

on: pull_request
Gradle Wrapper Validation
6s
Gradle Wrapper Validation
Gradle Plugin Publication Validation
0s
Gradle Plugin Publication Validation
Matrix: Gradle Build without Publish
Gradle Build and Publish
0s
Gradle Build and Publish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Gradle Wrapper Validation
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
Gradle Build without Publish (8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Gradle Build without Publish (21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Gradle Build without Publish (17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/