[resolved] Best practices Subversion SVN in TIS Team Edition

[Aquagest]

Hello everybody,
I am setting up the environment for Talend Integration Suite Team Edition for my company and use a SVN repository for code management.
Concerning SVN I have observed the following:
- In the Talend Administration Center I can create new project branches.
- In the Talend Integration Suite (TIS) I can raise a job's version number
- Whenever I save in TIS, it automatically raises the revision number
Here is what I am missing:
- I cannot revert to a revision of my choice
- I cannot comment a revision (put meaningful names as comment)
- I cannot visualize a history
- I cannot compare revisions or branches with each other
- ...
So my questions would be:
What are the best practices to work in a team?
How do you get the most of your SVN?
Should I install Subclipse or will that raise more problem than it solves?
If Subclipse is supported at all (I will not install a plugin that possibly corrupts my client), how do I install it? (I have seen posts suggesting copying .jar files etc. manually and I have seen posts recommending not to do so...)
Any help on this matter is greatly appreciated.
Thank you
- Aquagest

[Anonymous · Accepted solution]

Hello
Talend Studio is not a SVN client tool, so we can use other svn client tool to use revision control, here I recommend the TortoiseSVN one of svn client tool. You can download it from this website http://tortoisesvn.net/downloads
TortoiseSVN is a really easy to use Revision control / version control / source control software for Windows. With it, I can view the history , revert to a specify revision, compare revision to previous revision. I show the steps to use TortoiseSVN :
1. Download the TortoiseSVN from the link http://tortoisesvn.net/downloads.
2. Install TortoiseSVN(need to restart computer).
3. Check out project to a directory on local machine.
4.1. View the history of project. open the directory and right click on any place, select TortoiseSVN-->Show log to view history(see pic1,2),
4.2. Revert to a revision. A. open the directory and right click on any place, select TortoiseSVN-->Show log to view history, right click on the select revision and select 'Revert to a revision' (see pic3), and then right click on the project folde and select "SVN commit" to commit the changes).
4.3. Compare revisions with previous revision. (see pic4,5)

- I cannot comment a revision (put meaningful names as comment)

We can't add a comment to a revision on the studio when a new revision is commit, the comment is added by default like this (if you show the log of history on TortoiseSVN, you could see that):
when you save the job:
User 'admin@company.com' at 16:29:31 CST 2010-09-20 :
Save process item 'job1' at path '' in project 'p3'
if you create a new job:
User 'admin@company.com' at 16:27:29 CST 2010-09-20 :
User action : Create job
Create process item 'job1' at path '' in project 'p3'
Save process item 'job1' at path '' in project 'p3'
etc....

Best regards
Shong

[desarrollo_mine]

Dear Shong,
Thank you for your detailed reply and sorry for the delay, it has taken me quite a while to do some testing on the suggestions you have made.
In point 3 ("Check out project to a directory on local machine."), do you actually use a Remote connection to your Talend Administration Center and select the desired project from the pull down menu? Or do you use TortoiseSVN to check out the project to your local workspace and open it with Talend using the "Local" option?
It appears to me that (if we use the Talend "remote" connection) your suggestion works technically but in practice is likely to get messy. The Talend auto-commit just spams the SVN log and having zillions of automatically created revisions (plus the lack of adding meaningful comments) makes it hard to determine which revision to revert to if something goes wrong. Also, comparing revisions with each other is not as pretty as it should be (TortoiseSVN can obviously only offer displaying the XML differences of the .item and .property files, Talend's "Compare Job" option shows the differences in a much more visual way, but I MUST have previously created a new version/branch). Am I missing something here? Is the use of TortoiseSVN REALLY the widely suggested "best practice"?

[Anonymous]

Hello,
I'm trying to use Subversion with TIS TE 4.03.
I figure out how to activate commit comment in Talend Studio => in Talend admin center I have checked "SVN User Log" on my project so that each action in the design or metada request a comment.
Is that the good way ?

[Anonymous]

Hello

Is that the good way ?

Yes, if you want to commit comment when committing change, you need check the 'SVN User Log' box.
Best regards
Shong

[Anonymous]

Hello quagest_Alex

In point 3 ("Check out project to a directory on local machine."), do you actually use a Remote connection to your Talend Administration Center and select the desired project from the pull down menu?

Yes, I create remote connection and open remote projects in studio every day. I only use TortoiseSVN to read the history log sometimes and revert to old revision if needed.
Best regards
Shong

[Anonymous]

Hi,
Is it also possible to create an SVN tag in Talend open studio? (we have the commercial version).
Normally with Java coding, just before a release to the Acceptance enviroment we will create a SVN Tag of the code with a comment, how can I do the same in Talend?

[Anonymous]

Why is the option listed in "SVN History"  --> CheckOut, if it was never intended to rollback to previous revisions?
Additionally, the "feature" attempts to check out a previous revision, but errors out with 'unable to perform checkout while job is locked'...or it simply does not roll it back.  The title on the job window briefly flashes to a previous revision number before the current is re-loaded.
It seems very clear to me that it was intended to check out previous revisions...it is just broken or incomplete.  V5.3.1(with various patches)

[txpet2]

Is there a way to turn off the svn auto-commit feature?

[_AnonymousUser]

@txpet2
If you're trying not to commit to SVN, you don't need to use the remote connection to the project. 
Access the project in offline mode: