Skip to content
This repository was archived by the owner on Feb 21, 2025. It is now read-only.

Build scan URL not captured when cache disabled #139

Closed
bigdaz opened this issue Jan 17, 2022 · 0 comments · Fixed by #140
Closed

Build scan URL not captured when cache disabled #139

bigdaz opened this issue Jan 17, 2022 · 0 comments · Fixed by #140
Assignees
@bigdaz
Labels
bug Something isn't working
Milestone
v2.1.1

Comments

@bigdaz
Copy link
Member

bigdaz commented Jan 17, 2022

When cache-disabled: true is configured, then we fail to add required init-scripts to the Gradle User Home, resulting in build-scan URLs not being captured.
@bigdaz bigdaz self-assigned this Jan 17, 2022
@bigdaz bigdaz added the bug Something isn't working label Jan 17, 2022
@bigdaz bigdaz added this to the v2.1.1 milestone Jan 17, 2022
@bigdaz bigdaz mentioned this issue Jan 17, 2022
Merged
bigdaz added a commit that referenced this issue Jan 19, 2022
@bigdaz
Merge pull request #140 from gradle/cache-disable

Verified

This commit was signed with the committer’s verified signature.
bigdaz Daz DeBoer
GPG key ID: DD6B9F0B06683D5D
Verified
Learn about vigilant mode
a8da4e5 
Fix Build Scan capture when cache is disabled

With the change to use init-scripts to inject Build Scan capture, this functionality broke when caching was disabled and Gradle User Home wasn't initialized.

This PR fixes a couple of issues and ensures that the Gradle User Home is initialized even when it is not restored from the GitHub Actions cache.

Fixes #138 
Fixes #139
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bigdaz bigdaz

Labels
bug Something isn't working
Projects
None yet
Milestone
v2.1.1
Development

Successfully merging a pull request may close this issue.

Fix Build Scan capture when cache is disabled gradle/gradle-build-action
1 participant
@bigdaz