mirror of
https://github.com/gradle/actions.git
synced 2025-08-18 23:01:27 +08:00
ed4d086d37
Now, a `dependency-submission` step will trigger a dependency-graph generation, even if it follows a `setup-gradle` step in the workflow. Similarly, a `setup-gradle` step with `dependency-graph` configured will function as expected even if it follows a `setup-gradle` step.
42 lines
1.5 KiB
TypeScript
42 lines
1.5 KiB
TypeScript
import * as core from '@actions/core'
|
|
import * as setupGradle from '../setup-gradle'
|
|
import * as dependencyGraph from '../dependency-graph'
|
|
|
|
import {getDependencyGraphOption} from '../input-params'
|
|
import {PostActionJobFailure} from '../errors'
|
|
|
|
// Catch and log any unhandled exceptions. These exceptions can leak out of the uploadChunk method in
|
|
// @actions/toolkit when a failed upload closes the file descriptor causing any in-process reads to
|
|
// throw an uncaught exception. Instead of failing this action, just warn.
|
|
process.on('uncaughtException', e => handleFailure(e))
|
|
|
|
/**
|
|
* The post-execution entry point for the action, called by Github Actions after completing all steps for the Job.
|
|
*/
|
|
export async function run(): Promise<void> {
|
|
try {
|
|
if (await setupGradle.complete()) {
|
|
// Only submit the dependency graphs once per job
|
|
await dependencyGraph.complete(getDependencyGraphOption())
|
|
}
|
|
} catch (error) {
|
|
if (error instanceof PostActionJobFailure) {
|
|
core.setFailed(String(error))
|
|
} else {
|
|
handleFailure(error)
|
|
}
|
|
}
|
|
|
|
// Explicit process.exit() to prevent waiting for promises left hanging by `@actions/cache` on save.
|
|
process.exit()
|
|
}
|
|
|
|
function handleFailure(error: unknown): void {
|
|
core.warning(`Unhandled error in Gradle post-action - job will continue: ${error}`)
|
|
if (error instanceof Error && error.stack) {
|
|
core.info(error.stack)
|
|
}
|
|
}
|
|
|
|
run()
|