Five Stars

Upgrading Talend to 7.0

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

1 ACCEPTED SOLUTION

Accepted Solutions
Six Stars

Re: Upgrading Talend to 7.0

It depends off your overall architecture to be honest.
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.

 

Your production shouldn't be affected (best practice is to publish to Nexus which let your SVN independent of any job being run).

 

If you take a step backward, your SDLC should be:

  • Develop on Studio
  • Commit to SVN
  • Compile from SVN to Nexus (or straight to TAC decommisionned on v7)
  • Deploy and Schedule your job in Job Conductor which take your archive from Nexus to Job Server

Last step mean that your archive (compiled job) live in your Job Server independently of your SVN.

 

2 REPLIES
Six Stars

Re: Upgrading Talend to 7.0

It depends off your overall architecture to be honest.
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.

 

Your production shouldn't be affected (best practice is to publish to Nexus which let your SVN independent of any job being run).

 

If you take a step backward, your SDLC should be:

  • Develop on Studio
  • Commit to SVN
  • Compile from SVN to Nexus (or straight to TAC decommisionned on v7)
  • Deploy and Schedule your job in Job Conductor which take your archive from Nexus to Job Server

Last step mean that your archive (compiled job) live in your Job Server independently of your SVN.

 

Five Stars

Re: Upgrading Talend to 7.0

Thanks Adrien, that helped.