gradle/actions
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
actions/NOTICE

12 lines
723 B
Plaintext
Raw Permalink Normal View History

Extract caching logic into a separate `gradle-actions-caching` component (#885) With this change, the caching functionality of `setup-gradle` and `dependency-submission` is now provided by `gradle-actions-caching`, a closed-source library distributed under our [Terms of Use](https://gradle.com/legal/terms-of-use/). The rest of the action implementation remains open source. Using `setup-gradle` or `dependency-submission` with caching enabled involves loading and using the `gradle-actions-caching` component, requiring acceptance of the [Terms of Use](https://gradle.com/legal/terms-of-use/). There are no functional changes to caching provided by these actions: all workflows will continue to function as before. The non-caching aspects of action implementation remain open source. By running these actions with caching disabled they can be used without ever loading `gradle-actions-caching` or accepting the license terms. Supporting the caching infrastructure in this project requires a substantial engineering investment by Gradle Technologies, which we can sustain thanks to Develocity, our commercial offering. Caching technologies are a core part of the Develocity offering, and the caching in `setup-gradle` fits squarely in that space. This licensing change lets us continue to build advanced capabilities that go beyond what we would offer as open source. Proper production-ready Configuration Cache support will be the first capability. Improving build performance for self-hosted runners will follow. We may introduce functionality restrictions in future updates. However, caching functionality will remain free for public repositories. We have a long-standing commitment to open source, as maintainers of Gradle Build Tool, and by [sponsoring the open source community](https://gradle.com/oss-sponsored-by-develocity/) with free Develocity licenses. Public repositories are primarily used by open source projects, and we remain committed to supporting them. - Implementation of caching logic to save and restore Gradle User Home content has been removed, replaced by the `gradle-actions-caching` component. - The `@actions/caching` library is still used to cache Gradle distributions that are downloaded and provisioned by `setup-gradle`. This PR updates to the latest version of `@actions/caching`, and removes the patch that is no longer required. - License notices are now displayed in documentation, logs and the generated Job Summary.
2026-03-18 14:57:27 -06:00
NOTICE
The software in this repository, except for the bundled `gradle-actions-caching` component, is licensed under the MIT License.
The caching functionality in this project has been extracted into `gradle-actions-caching`, a proprietary commercial component that is not covered by the MIT License for this repository.
Add open-source 'basic' cache provider and revamp licensing documentation (#930) ## Summary - **New `basic` cache provider**: Adds an open-source (MIT-licensed) caching implementation built on `@actions/cache` as an alternative to the proprietary Enhanced Caching. Users can opt in with `cache-provider: basic` on both `setup-gradle` and `dependency-submission` actions. - **Revamped licensing & distribution docs**: Replaces the verbose licensing notice block (previously shown in README, docs, and logs) with a friendlier callout and a new dedicated [DISTRIBUTION.md](./DISTRIBUTION.md) covering component licensing, usage tiers, data privacy ("Safe Harbor"), and opt-out instructions. - **Improved messaging**: Enhanced Caching and Basic Caching each display concise, informative log messages and job summary notes instead of the previous wall-of-text license warning. - **New integration tests**: Adds `integ-test-basic-cache-provider.yml` workflow that seeds and verifies the basic cache provider across platforms, plus unit tests for `BasicCacheService` and `getCacheService` selection logic. - **CI workflow reorganization**: Dependency-submission integration tests extracted into their own reusable suite (`suite-integ-test-dependency-submission.yml`); sample project tests moved into the caching suite. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-02 21:36:01 -06:00
The `gradle-actions-caching` component is used only when enhanced caching is enabled and is not loaded or used with basic caching or when caching is disabled.
Extract caching logic into a separate `gradle-actions-caching` component (#885) With this change, the caching functionality of `setup-gradle` and `dependency-submission` is now provided by `gradle-actions-caching`, a closed-source library distributed under our [Terms of Use](https://gradle.com/legal/terms-of-use/). The rest of the action implementation remains open source. Using `setup-gradle` or `dependency-submission` with caching enabled involves loading and using the `gradle-actions-caching` component, requiring acceptance of the [Terms of Use](https://gradle.com/legal/terms-of-use/). There are no functional changes to caching provided by these actions: all workflows will continue to function as before. The non-caching aspects of action implementation remain open source. By running these actions with caching disabled they can be used without ever loading `gradle-actions-caching` or accepting the license terms. Supporting the caching infrastructure in this project requires a substantial engineering investment by Gradle Technologies, which we can sustain thanks to Develocity, our commercial offering. Caching technologies are a core part of the Develocity offering, and the caching in `setup-gradle` fits squarely in that space. This licensing change lets us continue to build advanced capabilities that go beyond what we would offer as open source. Proper production-ready Configuration Cache support will be the first capability. Improving build performance for self-hosted runners will follow. We may introduce functionality restrictions in future updates. However, caching functionality will remain free for public repositories. We have a long-standing commitment to open source, as maintainers of Gradle Build Tool, and by [sponsoring the open source community](https://gradle.com/oss-sponsored-by-develocity/) with free Develocity licenses. Public repositories are primarily used by open source projects, and we remain committed to supporting them. - Implementation of caching logic to save and restore Gradle User Home content has been removed, replaced by the `gradle-actions-caching` component. - The `@actions/caching` library is still used to cache Gradle distributions that are downloaded and provisioned by `setup-gradle`. This PR updates to the latest version of `@actions/caching`, and removes the patch that is no longer required. - License notices are now displayed in documentation, logs and the generated Job Summary.
2026-03-18 14:57:27 -06:00
Update license link for gradle-actions-caching component
2026-04-03 07:47:03 -06:00
Use the `gradle-actions-caching` component is subject to a separate license, available at license/gradle-actions-caching-license.txt.
Add open-source 'basic' cache provider and revamp licensing documentation (#930) ## Summary - **New `basic` cache provider**: Adds an open-source (MIT-licensed) caching implementation built on `@actions/cache` as an alternative to the proprietary Enhanced Caching. Users can opt in with `cache-provider: basic` on both `setup-gradle` and `dependency-submission` actions. - **Revamped licensing & distribution docs**: Replaces the verbose licensing notice block (previously shown in README, docs, and logs) with a friendlier callout and a new dedicated [DISTRIBUTION.md](./DISTRIBUTION.md) covering component licensing, usage tiers, data privacy ("Safe Harbor"), and opt-out instructions. - **Improved messaging**: Enhanced Caching and Basic Caching each display concise, informative log messages and job summary notes instead of the previous wall-of-text license warning. - **New integration tests**: Adds `integ-test-basic-cache-provider.yml` workflow that seeds and verifies the basic cache provider across platforms, plus unit tests for `BasicCacheService` and `getCacheService` selection logic. - **CI workflow reorganization**: Dependency-submission integration tests extracted into their own reusable suite (`suite-integ-test-dependency-submission.yml`); sample project tests moved into the caching suite. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-02 21:36:01 -06:00
For a detailed breakdown of components, licensing tiers, and data privacy terms, see DISTRIBUTION.md.
Reference in New Issue Copy Permalink