Dynamic ClearCase Views with TeamCity

I am having issues creating VCS roots that point to dynamic views in BASE ClearCase on a linux server. It seems to be a new issue with TeamCity 4.

On the linux server, the same server that hosts TeamCity, I start the view myview. This creates the view root directory /view/myview/.

On the New VCS Root screen, I enter /view/myview/vobs/dir1 as my view path and choose BASE as the ClearCase type. I then test the connection.

In TeamCity 3.1.2, the connection is successful with the following message: Connection Successful! directory version "/view/myview/vobs/dir1@@/main/12" and the message continues to list some details about the directory.

In TeamCity 4.02, I get the following error message directly below the view path text box: Invalid path: '/view/myview/vobs/dir1'; cannot find view root, directory containing 'view.dat' file

This view root does not contain a view.dat file. It appears from the following article that view.dat files are only associated with Snapshot views (http://www-01.ibm.com/support/docview.wss?uid=swg21204161). This is a dynamic view. In addition, it appears that a snapshot view on linux, the file be named ".view.dat".

Has TeamCity 4 dropped support for dynamic views? If not, any ideas on how I can get my view root to be accepted?

5 comments

Jason,

Thank you for brining our atention to the case. The responsible developer will be available next week and will investigate the issue.

As I see in the code the check was there already in 3.1.2 but it may not worked before for some reason.

--
Best regards,

Yegor Yarko
Project Manager (TeamCity)
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Jason,

View root finding algorithm in TeamCity 4.0.2 is the same as in TeamCity 3.1.2. Actually it finds both files "view.dat" and ".view.dat" so error message is incorrect.

Since this algorithm only checks the existing of the file without reading its content the workaround is to create empty "view.dat" or ".view.dat" file in the view root directory.

Later I will make ClearCase settings improving that removes the necessity of this algorithm at all, you can find this issue in our tracker: http://jetbrains.net/tracker/issue/TW-7192

0

Thanks for looking into the issue and for the response.

View root finding algorithm in TeamCity 4.0.2 is the same as in TeamCity 3.1.2.

If that's the case, perhaps something else is going on here, because I have zero problems creating a VCS root in 3.1.2 and cannot make it work in 4.0.2. I am using the same machine, the same View Root path, the same everything in both cases.

Since this algorithm only checks the existing of the file without reading its content the workaround is to create empty "view.dat" or ".view.dat" file in the view root directory.

Thanks for the suggestion. I have tried this and I still get the same error message. It persists whether the empty .view.dat file is a ClearCase element or not, or whether I have a ".view.dat" or just "view.dat" file.

When a ClearCase view is started on linux, the files in that fiew are accessible through /view/<view-name>/vobs/<dir>...
When you actually set a view in linux Clearcase, you can access the files simply through /vobs/<dir>...

Whether I start TeamCity from outside a specific view or from inside a view, and whether I try the /view/<viewname>/vobs/... route or (from within a view) the /vobs/... route, I get the same error message:

Invalid path: '/vobs/fct_apps/aa'; cannot find view root, directory containing 'view.dat' file

Is there anything else to look for? I'd really like to use TeamCity for build management, most likely the Enterprise Edition, but if I can't get it to work with the basic free edition, there's no way the Enterprise purchase will be approved.

0

Jason,

It is very strange... Did you create this file exactly in "/view/<viewname>" directory?

0

Aha! Thank you, I misunderstood the workaround. The root for my code is /view/view-name/vobs/dir1/dir2. I was creating the .view.dat file there instead of /view/view-name/.

That seems to have done the trick. I will let you know if I have any further issues with the ClearCase integration.

Thanks again!

0

Please sign in to leave a comment.