Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Folks,
Talend offers download sites that hold all and latest patch versions and Studio checks those regularly.
Whenever a new version becomes available, you get notified and asked to upgrade.
As the team first needs to test these versions, this upgrade should better be handled via a local repository instead of the centralized Talend version.
My requirement is :
1.Whenever a new version is there to upgrade it shouldn't pop up the notification, I should manually want to test and upgrade in a particular repository so, is there any method or tutorial on this please share me.
2.
how to set up a local proxy version holding the patches, any one suggest me on this. currently we are using JFrog artifact.
Hi @Vijay Bakkashetti,
I believe that this guides you through the process of setting up a proxy version....
https://help.talend.com/r/en-US/8.0/installation-guide-data-fabric-windows/setting-up-update-repositories-by-creating-proxy-repositories
When testing, using the test mode will create you a test branch for your code. The update can be tested there and when you are happy that it causes you no issues, you can carry out the update on your main branch.
I don't believe this is currently a feature.....but I could very well be wrong. I have raised this with the team and have suggested a feature request if this is not available. Sorry I am unable to conclusively answer this now, but my expertise is more aligned with building with the products.
Sorry for the delayed response @Vijay Bakkashetti. I have been speaking with one of our product managers and he came back to me with these features that I wasn't actually aware of.....
In our 2022-04 release we added a test mode from the update pop-up so that users can test the patches: https://help.talend.com/r/en-US/Cloud/release-notes/r2022-04-studio-new-features
Look for the "Studio can now automatically create test branches to test the migration of remote projects" feature. It allows you to test updates on a test branch first. This does not solve your complete requirement on its own, but I thought it would be worth mentioning.
The requirement to be able to control when your users see patches (which have been tested by you) should be able to be fulfilled with this recent change.....
Thanks for your response @Richard Hall. My requirement also, how to set up a local proxy version holding the patches, currently we are using JFrog artifact.
as an administrator if I will apply patches in TMC, then it will reflect to all developers studio or it's effected only my studio.
Hi @Vijay Bakkashetti,
I believe that this guides you through the process of setting up a proxy version....
https://help.talend.com/r/en-US/8.0/installation-guide-data-fabric-windows/setting-up-update-repositories-by-creating-proxy-repositories
When testing, using the test mode will create you a test branch for your code. The update can be tested there and when you are happy that it causes you no issues, you can carry out the update on your main branch.