Jump to content

Using SCC in LabVEIW


Recommended Posts

Hello, your company uses SVN Server as SCC and TortoiseSVN as front end for it. I bought the PushOK plug in to be able to use SVN directly from LV Project Manager. It seems to work, but I get some problems in understanding it.

My questions are:

1) Which architecture do you use in repositories?

2) I or we use this one:

Local path of a project is e.g C:\MyFiles\LVProjects\TestPrj

So the main module in rep is:

TestPrj\trunk (the current copy of the project)

TestPrj\branches (versions of the project)

TestPrj\tags (releases of the project)

What is the best way to set up SCC in LabVIEW to realize this architecture?

3) If I create a new project I do project-specific settings for SCC:

main-module for Project-Repository is TestPrj\trunk

branches and tags directories will be automaticaly detected

But the local path too ( C:\MyFiles\LVProjects\TestPrj\trunk ), but this is wrong, so I have to change it manually. Any better ways to make it automatically?

4) How can I get any older version of my project from the repository-server? Should I delete my current Project-Directory and check out version I need in the empty directory? I think I get some problems on this step. How do you do this? Can you explain me please?

5) Are there any tutorials how to use SCC in LabVIEW rightly?

Thank you in advice, Eugen

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.