If you are on a version of GoCD >= 16.7, the agent config `/etc/default/go-agent` will not have a JVM path in it. If you have a JVM path in it, you likely upgraded from an older agent, please remove it before upgrading and the agent and server should pick up the JVM on the $PATH.
If you have several JVMs and want to force the agent to use a specific JVM, use GO_JAVA_HOME to point to the JVM you'd like the agent to use. On Mon, Sep 18, 2017, 6:37 PM <[email protected]> wrote: > We are looking to upgrade some of our RHEL 7.2 boxes to RHEL 7.3. these > servers are GoCD Agents. I wanted to know what the best practice is for > this process with regards to GoCD agents (we have the GoCD server on > Windows 2012 R2). We typically upgrade all packages via yum during this > process, this would include Java. If we do this the GoCD agent will fail to > start as it has a specified java path in the configuration. Could you > confirm what the best practice is with regards to handling package updates > on Linux and GoCD? I assume it's 1 of 2 ways: > > > 1. Exclude Java has part of our update and let GoCD upgrade the Java as > part of upgrading the GoCD server. > 2. Upgrade Java using yum it and re-point the GoCD agent at the new > version. > > > How have the community handled kernel upgrades with a GoCD Agent? > > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
