Preferences for source control

[Sima]

Hi, I'd just like to get some input on what people are using for source control and what their likes and dislikes are. We are currently evaluating Perforce, and things seem to be going OK. Is there anything I should be looking out for?

Thanks.

[TroyK]

Check out this developer zone article...http://zone.ni.com/devzone/cda/tut/p/id/4633 

As long as you are using the LabVIEW Professional Development System, you can integrate your source control into LabVIEW.

Rational ClearCase is the tool I am using, but I only have the Full Development system so it isn't integrated.

ClearCase is fine, but using it for LabVIEW without having the Professional Development system is a pain.

Message Edited by Troy K on 03-11-2008 10:33 AM

[parthabe]

Hi Sima,

I ve used MS VSS with LV 7.1 externally.

Now, it gets configured into LV 8.5 seamlessly without any problem.

In general, MS VSS is enough unless & until there are so many development teams working across globally; because it is said that it has some serious problems with networks.

[Sima]

Thanks for the replies.

We've sometimes noticed that you have to refresh or go to Perforce and Get the latest revisions manually, even after you Check Out a file, which I thought would automatically get the latest revision. Is this normal? What buggy things happen for you in ClearCase or MS VSS?

Also, can you comment on the administrative side of either one? Perforce seemed pretty easy to install server-side, and hasn't required much administration so far. We are a small group, so we don't have a separate administrator for source control software.

[Sima]

Does anyone know whether TortoiseSVN is integrated into LV, or do you have to check in/out from its interface in Windows Explorer?

[Van_L]

Hi Sima,

If you want more information about Using Source Control Software with LabVIEW this is an awesome tutorial

Hope this information helps a little bit

[parthabe]

Hi Sima,

We re also exploring the possibility of integrating TortoiseSVN in our company.

From the presentation we had a few days back, it appears to be encouraging to be integrated into LV itself. But, I m not so sure as of now.

I shall update here once we re thro' the entire process.

[gmart]

Tortiose SVN is a standalone client for Subversion. It does not integrate with IDEs (including LabVIEW). It is an extension for Windows Explorer.

[parthabe]

Hi George,

Thanks for the info.

I thiunk the power point presentation was not clear to me completely.

[TCPlomp]

In order to use SVN (the SCC behind TortoiseSVN) inside LabVIEW, you will need a proxy.
PushOK is one of the options. I use it myself and it works just like MS VSS at work.

Ton