mirror of
https://github.com/gradle/actions.git
synced 2026-06-13 07:00:39 +00:00
a0ee12f71e
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.
135 lines
5.3 KiB
TypeScript
135 lines
5.3 KiB
TypeScript
import * as core from '@actions/core'
|
|
import * as exec from '@actions/exec'
|
|
import * as fs from 'fs'
|
|
import * as path from 'path'
|
|
import * as os from 'os'
|
|
import * as jobSummary from './job-summary'
|
|
import * as buildScan from './develocity/build-scan'
|
|
|
|
import {loadBuildResults, markBuildResultsProcessed} from './build-results'
|
|
import {getCacheService} from './cache-service-loader'
|
|
import {CacheOptions} from './cache-service'
|
|
import {
|
|
BuildScanConfig,
|
|
CacheConfig,
|
|
SummaryConfig,
|
|
WrapperValidationConfig,
|
|
getWorkspaceDirectory
|
|
} from './configuration'
|
|
import * as wrapperValidator from './wrapper-validation/wrapper-validator'
|
|
import {initializeGradleUserHome} from './gradle-user-home'
|
|
|
|
const GRADLE_SETUP_VAR = 'GRADLE_BUILD_ACTION_SETUP_COMPLETED'
|
|
const GRADLE_USER_HOME = 'GRADLE_USER_HOME'
|
|
|
|
export async function setup(
|
|
cacheConfig: CacheConfig,
|
|
buildScanConfig: BuildScanConfig,
|
|
wrapperValidationConfig: WrapperValidationConfig
|
|
): Promise<boolean> {
|
|
const userHome = await determineUserHome()
|
|
const gradleUserHome = await determineGradleUserHome()
|
|
|
|
// Bypass setup on all but first action step in workflow.
|
|
if (process.env[GRADLE_SETUP_VAR]) {
|
|
core.info('Gradle setup only performed on first gradle/actions step in workflow.')
|
|
return false
|
|
}
|
|
// Record setup complete: visible to subsequent actions and prevents duplicate setup
|
|
core.exportVariable(GRADLE_SETUP_VAR, true)
|
|
// Record setup complete: visible in post-action, to control action completion
|
|
core.saveState(GRADLE_SETUP_VAR, true)
|
|
// Save the Gradle User Home for use in the post-action step.
|
|
core.saveState(GRADLE_USER_HOME, gradleUserHome)
|
|
|
|
initializeGradleUserHome(userHome, gradleUserHome, cacheConfig.getCacheEncryptionKey())
|
|
|
|
const cacheService = await getCacheService(cacheConfig)
|
|
await cacheService.restore(gradleUserHome, cacheOptionsFrom(cacheConfig))
|
|
|
|
await wrapperValidator.validateWrappers(wrapperValidationConfig, getWorkspaceDirectory(), gradleUserHome)
|
|
|
|
await buildScan.setup(buildScanConfig)
|
|
|
|
return true
|
|
}
|
|
|
|
export async function complete(cacheConfig: CacheConfig, summaryConfig: SummaryConfig): Promise<boolean> {
|
|
if (!core.getState(GRADLE_SETUP_VAR)) {
|
|
core.info('Gradle setup post-action only performed for first gradle/actions step in workflow.')
|
|
return false
|
|
}
|
|
core.info('In post-action step')
|
|
|
|
const buildResults = loadBuildResults()
|
|
|
|
const gradleUserHome = core.getState(GRADLE_USER_HOME)
|
|
const cacheService = await getCacheService(cacheConfig)
|
|
const cachingReport = await cacheService.save(gradleUserHome, buildResults, cacheOptionsFrom(cacheConfig))
|
|
await jobSummary.generateJobSummary(buildResults, cachingReport, summaryConfig)
|
|
|
|
markBuildResultsProcessed()
|
|
|
|
core.info('Completed post-action step')
|
|
|
|
return true
|
|
}
|
|
|
|
function cacheOptionsFrom(config: CacheConfig): CacheOptions {
|
|
return {
|
|
disabled: config.isCacheDisabled(),
|
|
readOnly: config.isCacheReadOnly(),
|
|
writeOnly: config.isCacheWriteOnly(),
|
|
overwriteExisting: config.isCacheOverwriteExisting(),
|
|
strictMatch: config.isCacheStrictMatch(),
|
|
cleanup: config.getCacheCleanupOption(),
|
|
encryptionKey: config.getCacheEncryptionKey() || undefined,
|
|
includes: config.getCacheIncludes(),
|
|
excludes: config.getCacheExcludes()
|
|
}
|
|
}
|
|
|
|
async function determineGradleUserHome(): Promise<string> {
|
|
const customGradleUserHome = process.env['GRADLE_USER_HOME']
|
|
if (customGradleUserHome) {
|
|
const rootDir = getWorkspaceDirectory()
|
|
return path.resolve(rootDir, customGradleUserHome)
|
|
}
|
|
|
|
const defaultGradleUserHome = path.resolve(await determineUserHome(), '.gradle')
|
|
// Use the default Gradle User Home if it already exists
|
|
if (fs.existsSync(defaultGradleUserHome)) {
|
|
core.info(`Gradle User Home already exists at ${defaultGradleUserHome}`)
|
|
core.exportVariable('GRADLE_USER_HOME', defaultGradleUserHome)
|
|
return defaultGradleUserHome
|
|
}
|
|
|
|
// Switch Gradle User Home to faster 'D:' drive if possible
|
|
if (os.platform() === 'win32' && defaultGradleUserHome.startsWith('C:\\') && fs.existsSync('D:\\a\\')) {
|
|
const fasterGradleUserHome = 'D:\\a\\.gradle'
|
|
core.info(`Setting GRADLE_USER_HOME to ${fasterGradleUserHome} to leverage (potentially) faster drive.`)
|
|
core.exportVariable('GRADLE_USER_HOME', fasterGradleUserHome)
|
|
return fasterGradleUserHome
|
|
}
|
|
|
|
core.exportVariable('GRADLE_USER_HOME', defaultGradleUserHome)
|
|
return defaultGradleUserHome
|
|
}
|
|
|
|
/**
|
|
* Different values can be returned by os.homedir() in Javascript and System.getProperty('user.home') in Java.
|
|
* In order to determine the correct Gradle User Home, we ask Java for the user home instead of using os.homedir().
|
|
*/
|
|
async function determineUserHome(): Promise<string> {
|
|
const output = await exec.getExecOutput('java', ['-XshowSettings:properties', '-version'], {silent: true})
|
|
const regex = /user\.home = (\S*)/i
|
|
const found = output.stderr.match(regex)
|
|
if (found == null || found.length <= 1) {
|
|
core.info('Could not determine user.home from java -version output. Using os.homedir().')
|
|
return os.homedir()
|
|
}
|
|
const userHome = found[1]
|
|
core.debug(`Determined user.home from java -version output: '${userHome}'`)
|
|
return userHome
|
|
}
|