<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Version Control with Talend Open Studio ? in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340451#M108482</link>
    <description>you may be interested in this link on how to set this up for git 
&lt;BR /&gt; 
&lt;A href="http://richardlog.com/post/15939924496/putting-talend-open-studio-projects-under-version" rel="nofollow noopener noreferrer"&gt;http://richardlog.com/post/15939924496/putting-talend-open-studio-projects-under-version&lt;/A&gt; 
&lt;BR /&gt;this approach does have the problems that jlolling identified. You end up with a repository full of temporary items that change frequently and you don't need to keep. However, I have tried it and used it to restore a workspace. The trick here is that you need to close talend before syncing or you will create a locked workspace in the repository and so end up with a locked workspace when you restore.</description>
    <pubDate>Wed, 19 Mar 2014 20:35:23 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2014-03-19T20:35:23Z</dc:date>
    <item>
      <title>Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340446#M108477</link>
      <description>Hello,
&lt;BR /&gt;How can I Put Talend Open Studio projects under version control, I will need to enter the entire workspace into version control, including the hidden metadata and compilation directories (.metadata, .JETEmitters and .Java) .
&lt;BR /&gt;Regards
&lt;BR /&gt;Mbaroudi</description>
      <pubDate>Thu, 25 Jul 2013 15:42:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340446#M108477</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-07-25T15:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340447#M108478</link>
      <description>My experience is, it usually does not work this way. Adding .JETEmitters and .Java does not make sense because they contains only temporary created files.
&lt;BR /&gt;The main problem with "approach" is, you will not get notified about new jobs.
&lt;BR /&gt;The only way I know is to create a empty SVN repository and export your jobs with Export Items function into this directory and sync this with SVN. All others have to import this synced dir in they studios.
&lt;BR /&gt;It works but it is error prone.
&lt;BR /&gt;The best way is to contact a sales representive from Talend and order a small version (something like Team Edition)</description>
      <pubDate>Thu, 25 Jul 2013 16:39:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340447#M108478</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-07-25T16:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340448#M108479</link>
      <description>Thank you Jan,&lt;BR /&gt;I think that a solution will be possible when sharing the project directory and not the workspace.&lt;BR /&gt;Create the same name of project on Talend and lock some config file if necessary.  &lt;BR /&gt;Regards</description>
      <pubDate>Fri, 26 Jul 2013 09:05:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340448#M108479</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-07-26T09:05:32Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340449#M108480</link>
      <description>Jan - On your previous comment: 
&lt;BR /&gt;"The only way I know is to create a empty SVN repository and export your jobs with Export Items function into this directory and sync this with SVN. All others have to import this synced dir in they studios." 
&lt;BR /&gt;With this model, the developer has to export to svn at the end of the day (assuming he's the only working on the project that day) and manually re-import the job from svn into Talend every day? In doing the export, do you overwrite the existing or previous export? 
&lt;BR /&gt;So it sounds like you're saying that using svn to manage your TOS workspace or project directories directly is risky at best and error-prone? 
&lt;BR /&gt;Thanks for any guidance you may have on using svn with TOS. 
&lt;BR /&gt;Will</description>
      <pubDate>Wed, 19 Mar 2014 19:05:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340449#M108480</guid>
      <dc:creator>willm1</dc:creator>
      <dc:date>2014-03-19T19:05:30Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340450#M108481</link>
      <description>Yes you got it. Thats because companies usually decides to pay for the enterprise release &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;</description>
      <pubDate>Wed, 19 Mar 2014 20:31:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340450#M108481</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-03-19T20:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340451#M108482</link>
      <description>you may be interested in this link on how to set this up for git 
&lt;BR /&gt; 
&lt;A href="http://richardlog.com/post/15939924496/putting-talend-open-studio-projects-under-version" rel="nofollow noopener noreferrer"&gt;http://richardlog.com/post/15939924496/putting-talend-open-studio-projects-under-version&lt;/A&gt; 
&lt;BR /&gt;this approach does have the problems that jlolling identified. You end up with a repository full of temporary items that change frequently and you don't need to keep. However, I have tried it and used it to restore a workspace. The trick here is that you need to close talend before syncing or you will create a locked workspace in the repository and so end up with a locked workspace when you restore.</description>
      <pubDate>Wed, 19 Mar 2014 20:35:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340451#M108482</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-03-19T20:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control with Talend Open Studio ?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340452#M108483</link>
      <description>&lt;P&gt;Any news related to this feature in Talend Open Studio but updated to 2020? The last link to richardlog is broken.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance,&lt;/P&gt;
&lt;P&gt;Álvaro López&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 16:13:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Version-Control-with-Talend-Open-Studio/m-p/2340452#M108483</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-02-13T16:13:09Z</dc:date>
    </item>
  </channel>
</rss>

