infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-13643) Remove Gradle daemon in Buildbot
Date Sun, 19 Mar 2017 18:26:41 GMT

     [ https://issues.apache.org/jira/browse/INFRA-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin updated INFRA-13643:
--------------------------
    Status: Waiting for user  (was: In Progress)

Your build got further this time after I changed JAVA_HOME to a puppetised latest1.8 path.
So the JDK actually gets updated!

Failure here complains about Java, my paste below this Failure shows the jdk is working fine.

https://ci.apache.org/builders/ofbiz-trunk-framework/builds/49/steps/shell_2/logs/stdio 


 /usr/local/asfpackages/java/jdk1.8.0_121/bin/java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

Next step is yours to make :)


> Remove Gradle daemon in Buildbot
> --------------------------------
>
>                 Key: INFRA-13643
>                 URL: https://issues.apache.org/jira/browse/INFRA-13643
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot
>            Reporter: Jacques Le Roux
>            Assignee: Gavin
>
> When upgrading to Gradle 3 the daemon was let in place which is a default now.
> https://docs.gradle.org/current/userguide/gradle_daemon.html#when_should_i_not_use_the_gradle_daemon



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message