https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394785#M7905 <P>Thanks Adrien, that helped.</P> Thu, 31 May 2018 04:15:42 GMT Latha 2018-05-31T04:15:42Z https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394783#M7903 <P>While upgrading it is mandatory to stop svn, for me on the same SVN server 3 different repositories one for dev,QA and Prod are created, if i stop svn will it affect prod? I am migrating on test server</P> Sat, 16 Nov 2024 08:12:58 GMT https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394783#M7903 Latha 2024-11-16T08:12:58Z https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394784#M7904 <P>It depends off your overall architecture to be honest.<BR />Generally speaking, SVN is used a code control meaning that while your SVN is stopped to be upgraded none off your developers will be able to commit anything.</P> <P>&nbsp;</P> <P>Your production shouldn't be affected (best practice is to publish to Nexus which let your SVN independent of any job being run).</P> <P>&nbsp;</P> <P>If you take a step backward, your SDLC should be:</P> <UL> <LI>Develop on Studio</LI> <LI>Commit to SVN</LI> <LI>Compile from SVN to Nexus (or straight to TAC decommisionned on v7)</LI> <LI>Deploy and Schedule your job in Job Conductor which take your archive from Nexus to Job Server</LI> </UL> <P>Last step mean that your archive (compiled job) live in your Job Server independently of your SVN.</P> <P>&nbsp;</P> Tue, 29 May 2018 06:11:00 GMT https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394784#M7904 Anonymous 2018-05-29T06:11:00Z https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394785#M7905 <P>Thanks Adrien, that helped.</P> Thu, 31 May 2018 04:15:42 GMT https://community.qlik.com/t5/Installing-and-Upgrading/Upgrading-Talend-to-7-0/m-p/2394785#M7905 Latha 2018-05-31T04:15:42Z