Hello,
I'am currently working on a migration project from the v7.3 to the v8.0.1 of Talend MDM.
We set up our Vm's with the Infra Team and we are ready to begin the Upgrade.
We steel have some questions about :
1-The management of the Projects (in our GIT Repo) to migrate.
2-The management of artifacts already generated on Nexus server
After discussions and brain storming sessions, We :
1-We wrote a python script to Back up locally all projects from git Repo (Our Code with Version 7.3 of Talend is now Safe)
2- We asked from git Administrators to create the NEW_REPO_V8 and we will be pushing mirrors to that new repo with a python script. (At this point, source code in NEW_REPO_8 will still be in version 7.3)
3-We will open all projects (with the Studio V.8) One by one to confirm the migration when Talend detects the v7.3 source code.
- Is this the only way to Migrate (One by One) ?
4- If every thing works fine we push now the code to the old git repo which will host source code with v.8
5- Delete the Git repo which helped for the migration.
What do you think about this Strategy of git repo migration, is there any other approach ??
Now Regarding the Nexus server, we think that since we are upgrading version of Talend, it would be a better idea if we start with a blank nexus Server and we will be generating and building artifacts for our tasks One by one again (hundreds of artifacts) once the git migration is done. The nexus linked to the v.8 will be hosting only artifacts with source code v.8 .
- Same question here : Is this the only way to manage artifacts when version is different (One by One) ?
Thank you for reading and I'am waiting for your experiences with Talend "Migration/Upgrade"
