Upgrade Approach or Migration

Bala s

unread,

Mar 31, 2020, 3:43:41 AM3/31/20

to go-cd

Hi All - We are planning to upgrade Go Server, currently using 17.x version and planning to go for an upgrade 19.x version.

Have the following queries.

1) upgrade from 17.x to 18.x and then to 19.x - in-place upgrade

2) Setup a new instance with 19.x and migrate the content from the old one.

3) If step2 is followed, what is the best approach for data migration. Will the structure of data folder structure remains the same in new version.

If anyone knows or handled in their environment, please suggest.

Thanks,

Bala

Ketan Padegaonkar

unread,

Mar 31, 2020, 3:56:04 AM3/31/20

to go...@googlegroups.com

Either approach will work. In either case you should backup and shutdown your gocd server before doing anything else. The data folder structure has not changed between versions of GoCD. See the documentation about backup/restore about what is backed up, and what is not.

Also: there have been several breaking changes between 17.x and 20.x — so make sure to go through the release notes section on "breaking changes".

- Ketan

--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/3073702c-4559-46a8-8c30-7f41315e6774%40googlegroups.com.

Aravind SV

unread,

Mar 31, 2020, 6:05:28 AM3/31/20

to go...@googlegroups.com

Also: The version of Java that 17.x works with and the version that 20.x works with are different. Might need to watch out for that.

Bala s

unread,

Mar 31, 2020, 7:01:28 AM3/31/20

to go-cd

Thanks ketan and Aravind. Let me try out then.

Nikolay Kirov

unread,

Apr 2, 2020, 5:50:27 AM4/2/20

to go-cd

Hey Ketan,

Could you please advise how should we take on a migration if we have to? Our current setup is GoCD v17.5.0 based on 3.8 alpine image running on a docker container. We have couple of hundred of pipelines and rebuilding manually from scratch is highly inadvisable.

Thank you for your time.

Regards,

Nikolay

On Tuesday, March 31, 2020 at 8:56:04 AM UTC+1, Ketan Padegaonkar wrote:

Either approach will work. In either case you should backup and shutdown your gocd server before doing anything else. The data folder structure has not changed between versions of GoCD. See the documentation about backup/restore about what is backed up, and what is not.

Also: there have been several breaking changes between 17.x and 20.x — so make sure to go through the release notes section on "breaking changes".

- Ketan

On Tue, Mar 31, 2020 at 1:13 PM Bala s <write...@gmail.com> wrote:

Hi All - We are planning to upgrade Go Server, currently using 17.x version and planning to go for an upgrade 19.x version.
Have the following queries.

1) upgrade from 17.x to 18.x and then to 19.x - in-place upgrade
2) Setup a new instance with 19.x and migrate the content from the old one.
3) If step2 is followed, what is the best approach for data migration. Will the structure of data folder structure remains the same in new version.

If anyone knows or handled in their environment, please suggest.

Thanks,
Bala

--
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...@googlegroups.com.

Reply all

Reply to author

Forward