If you are finding in-place upgrades a problem, just wondering if you have tried customising connections. (If you have, then the rest of the information is not for you, I'm just trying to be helpful - apologies.)
Here is what I do to help. First I store all my projects in one folder (e.g. /user/my user name/workspace). As this is a MacOs thread, I am assuming readers will be on MacOS.
I then have all the project folders in there.
When I open Talend for the first time after installing a new version and it lists the projects to open, I click on Manage Connections. I then amend the connection with the location of the projects, my email address, my name, etc.
This stops Talend from storing all the projects in a sub-directory of its installation folder.
If they were historically in another folder, export them using the relevant version of Talend and a connection that pointed to their original location, restart Talend with the new connection and import them into their new home.
As this folder is constant from one upgrade to the next of Talend, the first time I open a project with a new version of Talend it upgrades the project. No more upgrade hell!
Several caveats:
1) This assumes that you want all projects working on the latest version of Talend that you have installed. (Although Talend will only upgrade jobs when you open them.)
2) If you only open projects with older versions of Talend they will not be upgraded. (Be careful as an older version of Talend cannot open a job after it has been upgraded.)
3) Ensure that you have superb backups if you are using multiple versions of Talend in case you commit an error and upgrade a job that you do not want upgraded.
For the most part this works, I have only had one project that did not survive the upgrade... but I did have superb backups.
As I say, that is my practice. If it helps, great!
