>
> Inside the install of the go agent look at config/wrapper-agent.conf
>
look for or add if it doesnt event,
set.GO_AGENT_JAVA_HOME=%GO_AGENT_JAVA_HOME%
as a pointer it does to where the jre folder resides not into the JRE its
self
Barry
--
You received this message because you are subs
Thank you Varsha for your reply. That's what I came to realize as well. I
will look at building my own image using docker gocd image as the base.
On Sunday, December 10, 2017 at 10:46:48 PM UTC-5, Varsha Varadarajan wrote:
>
> Hello,
>
> For the gocd agent to run, only the JRE is required and t
Hello,
For the gocd agent to run, only the JRE is required and that is why the
docker images only had the JRE installed. Since it is up to the user to
build anything they want, we only provided a minimal set of packages that
ensured that the gocd-agent ran. Usually, people use this as a base im
Hi Aravind,
Thanks for your reply and taking the time to check it out. After reading
your reply I was able to find out the root cause. There are 2 issues.
First, the docker image for go-cd agent of centos7 does not seem to have
the "which" command installed. The gradlew is basically a shell scr
Do you know if the "gradlew" task is somehow changing the PATH before it
executes gradle?
In the docker gocd-agent, I can see that JAVA_HOME is not set, but java is
available in /usr/bin. So, that shouldn't be a problem to run gradle.
On Thu, Dec 7, 2017 at 3:15 PM, Aver wrote:
> I've been tryi
I've been trying to debug this issue and noticed some interesting behaviour.
I've setup a pipeline with with 1 stage and following tasks:
- pwd
- echo $JAVA_HOME
- java -version
- sh gradlew clean build
The last task is the one that uses my gradle script to build the codes in
my repository.
My
