Hi Bala, I recommend letting the GoCD upgrade facilities take care of this for you. I would do the following:
1. Build a new server to replace your current 17.x one. 2. Install an appropriate version of Java that will work with both GoCD 17.x and 19.x. 3. Install GoCD server version 17.x (the same version as your current server. 4. Back up your current GoCD installation and restore it on the new server. 5. Upgrade the new server from 17.x to 19.x. If you follow this process then you should end up with a version of config.xml that contains all of the information of your current 17.x installation but in the correct format for 19.x. This is essentially what we did when we upgraded from 15.x to 18.x late in 2018. Hope this helps, Jason On Monday, 13 April 2020 07:50:24 UTC-4, Bala s wrote: > > Hello everyone, > > Recently i posted an upgrade approach and based on your inputs, i am able > to upgrade 19.x version from 17.x > However I could see there are a considerable changes in 19.x config.xml > tags(as how the elements represent for e.g plugin, pipeline tags), which is > getting failed, if I try to restore my older config.xml file. > > Please note that we have more than 1000+ pipelines, hence the content of > the file is huge. > > Can you please suggest, how to migrate the config.xml to the new version. > Is there any tool or add-on available. > > Appreciate your inputs. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/db6436a5-0929-4a2b-ba2b-0c6e8f168ded%40googlegroups.com.
