Skip to content
Pre Merge Checks

Fix not sending report if project reuses configuration cache and attachGradleScanId is true #68

Sign in to view logs

Fix not sending report if project reuses configuration cache and attachGradleScanId is true

Fix not sending report if project reuses configuration cache and attachGradleScanId is true #68

Triggered via pull request December 1, 2023 20:57
@wziebawzieba
opened #19
fix_gradle_scan_id_when_configuration_cache_enabled
Status Failure
Total duration 1m 36s
Artifacts –

pre-merge.yaml

on: pull_request
Matrix: gradle
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
gradle (ubuntu-latest)
Process completed with exit code 1.
gradle (windows-latest)
The operation was canceled.
gradle (macos-latest)
The operation was canceled.
gradle (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/