Going from 15.2 to 17.2 is a huge jump. I suggest going through the release notes to see breaking changes and known issues may affect you. The biggest one being that you now need java 8 on the agent and server machines.
On Thu, Mar 16, 2017 at 5:07 PM Diogo Oliveira < diogo.olive...@outsystems.com> wrote: > Hi everyone, > Still, I have some questions before I even attemp to test this upgrade: > > 1 --> I have custom ports on my Go Server and Agents. All of them > communicate through 80/443 instead of 8153/8154. Are these changes > preserved in the upgrade? Since the Go configurations changed in versions > after 15.2 (I checked that), will this still work? > If you're doing this by setting the variables GO_SERVER_PORT and GO_SERVER_SSL_PORT variables. The server should upgrade smoothly without any issues. We recommend that you compare the copy of /etc/default/go-server with the current one <https://github.com/gocd/gocd/blob/master/installers/go-server/release/go-server.default> that we have to see if anything needs changing. > 2 --> All of my Go Agents are running through command line and not as a > service, because I need them to be interactive. This is blocking for the > upgrade somehow? > The agent CLI has changed significantly since 15.2. The GO_SERVER and GO_SERVER_PORT variables that were used to connect the agent to the server have been deprecated - use GO_SERVER_URL instead. Additionally see this <https://docs.gocd.io/current/installation/ssl_tls/end_to_end_transport_security.html> to improve security. -- 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 go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
