Skip to content

Commit 4f21f04

Browse files
smjt-hHarness
authored andcommitted
fix: [CI-20520]: add missing gradle docs (#100935)
* 201c94 fix: [CI-20520]: add missing gradle docs
1 parent 9a97803 commit 4f21f04

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/continuous-integration/use-ci/caching-ci-data/cache-intelligence.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,6 +404,24 @@ Add the following snippet under the `<build>` section to configure the apache-ra
404404
</build>
405405
```
406406

407+
### Gradle cache location
408+
409+
Harness sets the following environment variable for Gradle builds:
410+
411+
```
412+
GRADLE_USER_HOME=/harness/.gradle
413+
```
414+
415+
As a result:
416+
417+
- All Gradle dependencies and caches are saved and restored from `/harness/.gradle` because `/harness` is a shared directory that can be accessed across all steps.
418+
- Cache Intelligence and the Save/Restore Cache steps are optimized for this path.
419+
- This location is different from the default Gradle cache location (`~/.gradle`).
420+
421+
:::info
422+
Cache Intelligence is not currently supported on local (self-managed) infrastructure.
423+
:::
424+
407425
Go to the [CI Knowledge Base](/docs/continuous-integration/ci-articles-faqs/continuous-integration-faqs) for questions and issues related to caching, data sharing, dependency management, workspaces, shared paths, and more. For example:
408426

409427
* [Why are changes made to a container image filesystem in a CI step is not available in the subsequent step that uses the same container image?](/docs/continuous-integration/ci-articles-faqs/continuous-integration-faqs#why-are-changes-made-to-a-container-image-filesystem-in-a-ci-step-is-not-available-in-the-subsequent-step-that-uses-the-same-container-image)

0 commit comments

Comments
 (0)