Configuring ClearCase for LV8

[Anonymous]

Hi,

I am trying to configure ClearCase to run with LV8. I have setup and
multiple different SCC programs (PVCS, VSS, Perforce, etc.) with LV8
but cannot figure out how to configure the directory and the project
for ClearCase.

Do I need to create a Project VOB or just a Project View? If I just
have a Base View is it possible to link ClearCase to LV?

Any help would be greatly appreciated.

Thanks.

Randy

[VCLifer]

I realize this doesn't help answer your question, but it may help lighten the mood of trying to get CC to work with LV8. 🙂

http://www.youtube.com/watch?v=qrKceAK0IL0

Sorry, this was just too funny to pass up. Good luck with it.

Z.

[Justin D]

Hi Randy,

I don't think it matters how things are set up in Clearcase specifically.  As long as LabVIEW can check files in and out through command line everything should work.  That being said, I haven't used LabVIEW with Clearcase myself.  I've only used Perforce with LabVIEW previously.

Regards,
Justin D

[RGSchmidt]

Still no luck using ClearCase with LV 8.2

Anyone within NI that verified its functionality who can post any ideas. I have been able to get LV to see the PVOB but can't get LV to add files without getting a CC error that the view was not created properly. (You have to love cryptic error messages)

Thanks.

Randy

[danny_t]

Randy,

If you are having problems with the LabView 8.0 ClearCase integration remember it is quite possible to just use LabView and ClearCase manually. We are working with LabView 7.0 and ClearCase and there is no integration for this, it is not as elegant as it could be but works fine. In truth the LabView specific problems will be basically the same with or without integration (cannot merge LabView VI's,  needing to checkout files other than the ones you edit due to recompiles)

In fact before attempting to integrate LV and CC is your ClearCase installation all setup and working OK ?

I would go further you can actually write your own VI to do ClearCase actions using CAL (see below), I have Vi that automatically checkout and check in files for builds.

The question about a project VOB or not, does not relate to how you use ClearCase with LabView but to whether you intend to use the ClearCase out of the box UCM set-up or Base ClearCase, both will work with LabView, I have used ClearCase (and been a ClearCase administrator) for many years and much prefer Base ClearCase you can do so much more with it.

You seem a little confused between VOBS and View so a little guide (sorry if you know all this)

ClearCase stores file elements, directory elements, derived objects and metadata in a repository called a VOB.

A Project VOB is a VOB which contains the additional information necessary for using Unified Change Management.

You will only need a Project VOB if you are using UCM.

A ClearCase View  is what determines what version of the file(s) you will be looking at in the VOB.

So in Base ClearCase you need at least one ClearCase VOB and at least one ClearCase View to operate.

Typically you will have many ClearCase view, we have a different view for every ClearCase branch and we use one branch per task. The View and branch combination are what gives your developers there isolation from each others changes. 

 

cheers

Dannyt

CAL

The ClearCase Automation Library is a COM interface you can use to access and manipulate ClearCase data on Windows platforms. You can use CAL to write scripts, stand-alone programs, or macros embedded in other applications. The usual ClearCase license checks apply to applications using CAL.

Message Edited by datman on 05-16-2007 03:08 AM

[danny_t]

Randy,

Just seen your second post to this.

As I do not use the LV 8.0 which integrates with CC, I cannot be certain, but  I would expect your View creation is NOT part of the integration.

I would very much expect that it is up to you to create your View in order to get the correct configuration specification for you branching structure, once your View is active and running and your VOB is mounted then the integration should work.

Before worrying about the Labview part of things,  first ensure that on your PC (I assume windows based) you can create a ClearCase view and through the ClearCase explorer you can checkin checkout  and add simple text files.

If you can do the above let me know the ClearCase error you are getting as an ex CC admin I may be able to help

Dannyt

[RGSchmidt]

Thanks for input but I want to integrate CC with LV.

The developers are not following the rules with seperately running apps so I need to force the issue. We have been creating and using Views for a long time. LV does not work with a VOB only a PVOB.

Any help in integrating the 2 would be greatly appreciated.

[danny_t]

Hello Again,

---

@RGSchmidt wrote:

Thanks for input but I want to integrate CC with LV.

The developers are not following the rules with seperately running apps so I need to force the issue. We have been creating and using Views for a long time. LV does not work with a VOB only a PVOB.

Any help in integrating the 2 would be greatly appreciated.

---

I felt sure this was incorrect;  a PVOB only has real meaning to ClearCase UCM and if a PVOB was needed then anybody using Base ClearCase (a far better way of working) would be unable to integrate LV and ClearCase. 

So I download the LabView 8.2.1 evaluation copy, installed it and started it up,  configured ClearCase as the source control system and it worked first time with no PVOB and no problems. I only have ClearCase VOBs as I hate UCM. :-)

I can checkout, checkin, see the VI history (ClearCase history that is).  There a quite a number of things you cannot do with the integration and as such will still often want to use the ClearCase explorer to be able to work. 

The only reference to UCM in the whole thing was an option in the Advance Settings window. In the Source Control Panel setting (LabView options), there is an advance button next to the "Source control provider name", in this Advance window under operations there is an option "Always prompt for an activity when working in a view of a ClearCase Project." that is an obvious reference to a UCM activity, but even with that still ticked Base ClearCase works fine.

My system is

Base ClearCase (not UCM)

VOB and View server are running on a Sun system

Client is on a  Windows XP box.

Steps I took (assumes familiar with ClearCase terms)

LV

    LV Source Control Panel   --- Source Control Provider Name -- ClearCase   --- all options can be left as default.

ClearCase

Using a normal VOB --  called ATS.

I have a number of ClearCase already views created. 

The Views need to be controlled vi ClearCase NOT LV,  use ClearCase explorer or Homebase or command line to create your views as you normally do. 

Ensure that your VOB is mounted (use ClearCase explorer)

Ensure your view have started and has been mounted. For example my view dannyt-test is mounted to drive P:

Navigate to your LabView VI's within ClearCase vi the View mount point - so P:\ATS\LVProject\

Open your VI, now the  in Tools -> source Control -> you can checkin / checkout the VI.

I have not tried using the View extended pathname method, but I would expect that to work as well.

As somebody who has worked as a build release manager and ClearCase administrator I would not expect the level of integration of LabView and ClearCase to solve your problem

Getting developers to follow rule  needs to be done with training, encouragement,  ClearCase triggers and a good source control process that is both clear and workable. The final item is a very large stick 🙂

What part specifically is not working for you ?  do you have any error messages ?

good luck 

cheers

Dannyt

[RGSchmidt]

Thanks.

I was able to get LV to at least recognize the Project and path (thought that I had tried this combination before going to the PVOB but evidently not) but I was still unable to add files to CC.

I get the following error (see attached file), unable to associate file with view. I am working local (c:) while all views are on a network mapped drive. Does this mean that I have to work on the network drive and have the files in a private view? All other SCC tools allow for newtork storage of files but allow developers to checkin/out from local drive, is there a problem with how the view is setup?

Randy

[danny_t]

Hi Randy,

Yes for ClearCase you need to work on the network drive where the views are mounted.  You error is due to the fact that Clearcase has not idea nor does it care about your files on the C: drive.  Is that a problems for you ?

 In ClearCase unless you are within a view context you cannot see  or access and files within a VOB. There are three ways to get into the 'view context'

• In Clearcase explorer you can create a view shortcut without mapping a network drive and access the files, but only from within the Clearcase explorer, so you can for example double click on a VI and it will open, you should be able to check it out and in ect. You can add files in the ClearCase explorer, but you will really be able to access it from out side ClearCase explorer, ie if you start LabView then try to open a VI in that VI it will not happen.
• The better option is to map your view to a network drive and work from that, now all all your noraml windows tools ect can find the VI's happily on your networked drive.
• When you setup your Clearcase I will have also created a view mount point normally on the M: drive, you can also navigate into your view and find your files from here, this is using the view extended pathname, I would not really go that way, unless you a very sure on what you are doing.

I say normal operation,  this assumes you are using ClearCase dynamic views. There is another option you could use ClearCase snapshot views.  But unless you have bought the ClearCase light version and have to use them, or have other specific reason for using snapshot views I would stick with dymanic ones.

You say you have been creating & using Views for a long time, do not take this the wrong way, but can I recommend  two possible ClearCase books, that may clarify some of this stuff.

The Art of ClearCase(R) Deployment: The Secrets to Successful Implementation (The Addison-Wesley Object Technology Series)

Software Configuration Management Strategies and Rational ClearCase: A Practical Introduction (TheADDP9 Object Technology Series) (Paperback)

I hope this helps

cheers

Dannyt