LabVIEW and SVN SCC

[Morten Pedersen]

Hi,

We are a company that develops test and

measurement systems, with LabVIEW and TestStand. We are working in the latest

and prior versions of the development systems.

We have in mind to change our existing source

code control (SCC) to the following toolchain in the latest

versions:

- Tigris Subversion Server on Linux (Tigris SVN)

- TortoiseSVN Client (to use SVN via file

explore)

- PushOK SVN Client (to use SVN from the

LV project

explore)

Does anyone have some Pros. and/or Cons.

Regarding this setup for company use with LabVIEW and

TestStand?

Best regards,

Morten Pedersen

[Ton Plomp]

QUOTE(Morten Pedersen @ Feb 8 2008, 11:24 AM)

Hi,

We are a company that develops test and

measurement systems, with LabVIEW and TestStand. We are working in the latest

and prior versions of the development systems.

We have in mind to change our existing source

code control (SCC) to the following toolchain in the latest

versions:

- Tigris Subversion Server on Linux (Tigris SVN)

- TortoiseSVN Client (to use SVN via file

explore)

- PushOK SVN Client (to use SVN from the

LV project

explore)

Regarding this setup for company use with LabVIEW and

TestStand?

I have a similar setup running, where the server is on a Linux Apache box, and I use a Subversion WIndows client for LabVIEW 6.x and 7.x and advanced techniques. For LabVIEW 8.x I use the PushOK Client.

Both work OK, but you should notice that anonymouse browsing should be disallowed to have the PushOK function correctly.

Be aware that if you want to build your own tool in LabVIEW 8.x with the built-in SCC api, the PushOK client gives pop-ups.

Ton

[Justin Goeres]

QUOTE(Morten Pedersen @ Feb 8 2008, 03:24 AM)

- Tigris Subversion Server on Linux (Tigris SVN)

- TortoiseSVN Client (to use SVN via file

explore)

That's my setup (everything but PushOK), and I've been very happy with it. No problems at all.