Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

Allen H
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 8, 2023

 

The pipeline has been set to disable the daemon, but the daemon is still enabled during the execution process, and an error is reported. What is the wrong setting?

 

The error message is as follows:

```

----- End of the daemon log -----
FAILURE: Build failed with an exception.
* What went wrong:

Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
* Try:

> Run with --stacktrace option to get the stack trace.

> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org

```

Pipeline yml :

- step:
name: building
script:
- export GRADLE_OPTS='-Dorg.gradle.daemon=false'
·····
      - ./gradlew publishBundle --track internal

1 answer

0 votes
Erez Maadani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 8, 2023

Hi @Allen H 

It's possible that your gradle daemon had started running before you exported the `GRADLE_OPTS`. Try stopping the daemon before calling your gradle command:

    script:
- export GRADLE_OPTS='-Dorg.gradle.daemon=false'
·····
- gradle --stop
      - ./gradlew publishBundle --track internal

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events