Hi, Fist of all, a mistake: it was from version 16.2.1 and not 15.2 :)
Regarding the ports GO_SERVER_PORT and GO_SERVER_SSL_PORT on the Server, I realized that they are only working if I launch the server from the command line. If I start it as a service, those as ignored. Is this what's supposed to happen? So, I ended up adding to wrapper-server.conf this: wrapper.java.additional.16=-Dcruise.server.port=80 wrapper.java.additional.17=-Dcruise.server.ssl.port=443 Will this solution "survive" to upgrades? If I then upgrade to a newer version will this be kept or erased? By the way, I have been doing some experiments already, upgrading from 16.2 to 17.3 already :) So, I hit the wall on something: --> I started by upgrading the server, so that agents update themselves; --> Things worked as I would expect, except one thing: I was expecting that, when agents auto upgrade, they would also upgrade the bundled jre (I'm using the bundled version), but apparently they didn't, since I started receiving the message "Unsupported major.minor version 52.0" when trying to launch the agents.(I read https://docs.gocd.io/current/installation/troubleshoot_installer.html already) --> I ended up pointing to a local installation of JRE8, but I would like to understand if it was supposed that the bundled jre was also upgraded (and then this is some kind of upgrade bug) of if this is expected. And if yes, what's the rationale? :) Thanks a lot for your help! :) quinta-feira, 16 de Março de 2017 às 11:53:51 UTC, Ketan Padegaonkar escreveu: > > 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 <[email protected] > <javascript:>> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
