Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Coming from 6.1 and doing an upgrade to 6.4 - The old repos were in SVN and an on the same server where the TAC ran. Is this possible using GIT ? I noticed in this article that one of the requirements is a "supported distribution of git". Does this mean my remotes must be constrained to one of those sites (bitbucket/github/gitlab)? I have tried to setup a local (to TAC) git repo then config a new project from the TAC pointing there but I haven't been successful yet.
yes, As iburtally said we have to export and import to the Whole Project from SVN to GIT.
A) Export the Project From old SVN Repository, and keep that ZIP file in a Known Location.
B) Create a Repository in GIT enterprise and Create a New Project in TAC using just Created GIT URL as a Source Code Repository.
C) Once the Project Created import the ZIP File.
D) Check the Code Components and binaries what exactly you had in the SVN.
I tried this procedure and i was succeed.
The supported and recommended Git versions are listed here for 6.4 https://help.talend.com/reader/LkoujqGSD5Fhf2ln8GInCg/vG6YH5w_LNZIlmyhlaggww
To have a supported environment, use only the versions listed. If you have a different version, please query Talend Support to find more.
You can use both SVN and Git with your TAC. However, there is no automatic SVN to Git conversion of your actual project. The supported way is to use the studio, connect to svn project, export the project, switch and connect to git project, and import the project.
@iburtally wrote:
The supported way is to use the studio, connect to svn project, export the project, switch and connect to git project, and import the project.
Can you please write more detailed steps? When you export the project, File/Export, what export destination do you select? How do you do import project? Do you create empty project in the git and in Talend studio you do File/Import?
Thank you very much for your help!
Hi Iburtally,
Can you please write more detailed steps? When you export the project, File/Export, what export destination do you select? How do you do import project? Do you create empty project in the git and in Talend studio you do File/Import?
Thank you very much for your help!
Yan
@iburtally wrote:
The supported and recommended Git versions are listed here for 6.4 https://help.talend.com/reader/LkoujqGSD5Fhf2ln8GInCg/vG6YH5w_LNZIlmyhlaggww
To have a supported environment, use only the versions listed. If you have a different version, please query Talend Support to find more.
You can use both SVN and Git with your TAC. However, there is no automatic SVN to Git conversion of your actual project. The supported way is to use the studio, connect to svn project, export the project, switch and connect to git project, and import the project.
yes, As iburtally said we have to export and import to the Whole Project from SVN to GIT.
A) Export the Project From old SVN Repository, and keep that ZIP file in a Known Location.
B) Create a Repository in GIT enterprise and Create a New Project in TAC using just Created GIT URL as a Source Code Repository.
C) Once the Project Created import the ZIP File.
D) Check the Code Components and binaries what exactly you had in the SVN.
I tried this procedure and i was succeed.
Thank you Rchallagundla for your reply!
Yes, I followed the steps and it succeed!
Yan
And I want to add few more points here for my Previous reply.
1) The above Mentioned Points is for trunk (SVN) Master (GIT) only, if you have Multiple Branches in SVN you need to Repeat this Procedure.
Thank you Rchallagundia! That helps!
Yan
But I want to keep mostly commit in svn. If I do like as you says, I can just have the last version. I can not all the details of commit's record in svn? how can I do to get it ?
Thanks a lots
best wishes
Hello zjing,
if you want to keep all the Versions from SVN there are Desktop tools outside (SVN to GIT tool) to track everything like history and versioning management.
but as far as i know SVN latest Version contains all the committed code in TRUNK till the migration date happened, so no need to migrate all teh versions until you have priority.