TC 4.0.2 and ClearCase build trigger.

Hello,

Do you see any changes in the Pending changes of the build configuration?
I am trying to figure out whther the problem is with changes detection or only with the build triggering.

Do you have clocks synchronized between TeamCity server and ClearCase server?

--
Best regards,

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

Do you see any changes in the Pending changes of the build configuration?

No, I was watching the project/build config closely as the change collection started. No activity.
As you can see from the vcs.log the checkin is detected. It was the file cs_th_develop.txt that was checked in.

Could it be some logic that won't trigger a make because of the .txt extension?

Do you have clocks synchronized between TeamCity server and ClearCase server?

Both machines uses NTP, so that should not be a problem.

My configuration settings are as follows: (note - a ClearCase view was set prior to starting TC on the linux machine, hence reference through /vobs instead of /view/viewtag/vobs)

I guess we will need larger part of teamcity-vcs.log covering "Collecting changes" messages for the build in question.

Also, could you please include the beginning of the build log if triggered manually?

It seems that you specified a directory within your ClearCase files as a working directory. Actually, a recommended way is to let TeamCity transfer the sources to the agent (agent can be a remote machine). If not controlled by TeamCity, the sources can get of of sync with the changes reported in the web UI for the build. Also, please note that when checkout mode is set to an option other then "Do not checkout files automatically", TeamCity assumes that it controls the directory and can delete the directory under some circumstances.

Is it the only ClearCase build configured on the TeamCity server?

Could you plase also describe how SDL-TH root is configured?

TIA,
Yegor Yarko

It seems that I have the same problem. With projects which use a basic /main/LATEST rule, everything is fine, all the modifications are detected and the build is triggered. But with the projects which use a more complex config_spec with branch, TC don't detect the modification. I've try with the 4.0.2 release and with the latest EAP (8804).
When I look at the log file, my modification seems to be reported by Clearcase (see below) but not take into account by TC, any idea ?

Log file:

[2009-04-02 15:55:10,505]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 02-April-2009.15:51:34 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic
[2009-04-02 15:55:10,724]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 02-April-2009.15:39:04 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic
[2009-04-02 15:55:11,052]   INFO - .clearcase.ClearCaseConnection - interactive execute: cleartool lsvtree -obs -all D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln  <= this is my modified file
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main 
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\0
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\0
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\1
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\2
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\3
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\4
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\5
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\6
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\7
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\8
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\9
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\10
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\11
[2009-04-02 15:55:11,099]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\12
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\13
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\14
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\15
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\16
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\17
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\18
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\19
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\20
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\21
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\22 (MAGIC_64I3.0d.73beta1, MAGIC_64I3.0d.x, MAGIC_64N3.0d.73beta1, MAGIC_N3.0d.73beta1)
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\23
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: D:\ccviews\LTR_s0003900_tv_snapshot_view\magic_src\magic\configNT\magic30_delivery.sln@@\main\dev3.0\24
[2009-04-02 15:55:11,115]   INFO - .clearcase.ClearCaseConnection - output line read: Command 1 returned status 0
[2009-04-02 15:55:11,130]   INFO - .clearcase.ClearCaseConnection - interactive execute: cleartool quit
[2009-04-02 15:55:11,130]   INFO -      jetbrains.buildServer.VCS - Finish collecting changes for magic_src/magic; 0 changes collected 0 changes reported <= but no TC reporting !!

I guess we will need larger part of teamcity-vcs.log covering "Collecting changes" messages for the build in question.

Attatched - search for 2009-03-16 in teamcity-vcs.zip

Also, could you please include the beginning of the build log if triggered manually?

Build failed, but that is not TC fault, see manstart.zip

It seems that you specified a directory within your ClearCase files as a working directory. Actually, a recommended way is to let TeamCity transfer the sources to the agent (agent can be a remote machine). If not controlled by TeamCity, the sources can get of of sync with the changes reported in the web UI for the build. Also, please note that when checkout mode is set to an option other then "Do not checkout files automatically", TeamCity assumes that it controls the directory and can delete the directory under some circumstances.

OK, but this all sounds a bit like CVS type of thinking. A checkout in ClearCase is very different from CVS. I guess TC should never need to check out and reserve a file from ClearCase, but I could be mistaken. :-)

Is it the only ClearCase build configured on the TeamCity server?

There are 3 other dormant ClarCase confs. defined.

Could you plase also describe how SDL-TH root is configured?

VCS Root Name
VCS root name:	Enter a unique name to distinguish this VCS root from other roots. If not specified, a name will be generated automatically.
Type of VCS
Type of VCS:	ClearCase CVS Perforce StarTeam Subversion

All I had time for today ...
Note copy paste insists that ClearCase Use is UCM, but the actual setting is Base.

Cheers

Thank you for the details.

I am afraid we will need a bit more info.
Namely:
- your config spec for the view in question
- clearcase integration debug logs as described in corresponding doc section.

I would ask you to enable the debug logging, add another change, click on Actions > Check for pending changes on a build configuration page, wait a bit and if the change does not appear in Pending changes, send us teamcity-vcs and teamcity-clearcase.log files together with the full file name you changed.

OK, but this all sounds a bit like CVS type of thinking. A checkout in ClearCase is very different from CVS. I guess TC should never need to check out and reserve a file from ClearCase, but I could be mistaken. :-)

By "checkout" here I meant retrieving the files from the version control, not marking for checkout/edit.

The problem with using your ClearCase view directory to run your build it that the view can be updated while the build is running and the changes displayed in TeamCity web UI may not include the changes used by the build. I'd recomment you to use "automatically on server" checkout mode and do not set build's working directory.

--
Best regards,

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

Fabrice,

Can you please gather the same information I asked Ole Morten in my last comment: clearcase integeration debug logs,  your config spec and full name of the file changed.


I've created an issue in our tracker: http://jetbrains.net/tracker/issue/TW-7767 it's more appropriate to attach all the data there (you can also send it to teamcity-feedback@jetbrains.com if you do not want to make it public).

--
Best regards,

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

Back from my Easter holliday ...

Tried to set VCS checkout mode to 'Automatically on server'
Left Checkout Directory blank
Left Working Directory blank
View path is set through /view/viewtag/vobs ...
Use ClearCase=BASE
Test Connection=successful
Starting a manual Run, yields:

Build log:
Checking for changes

Could not get project sources

In ClearCase log (note ConfigSpec is in there)
[2009-04-14 14:06:21,155]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - simple execute: cleartool catcs
[2009-04-14 14:06:21,414]  DEBUG [Cached pool 3] - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
element *                                                CHECKEDOUT
# BNS APP (Header files) (test1-4)
element /vobs/product/dxc_ip/xf_delivery/unpacked_files/...  CXCR102007_2-R14A03
# Delivery VOB handling
element -directory /vobs/product/dxc_ip/xf_delivery       /main/LATEST -nocheckout
element -directory /vobs/product/dxc_ip/xf_delivery/...  /main/LATEST
element /vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/...     /main/eto_improvement/LATEST # DCN_H source
element * /main/LATEST
element -directory * /main/LATEST
StdErr:------------
End----------------

[2009-04-14 14:06:21,422]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - simple execute: cleartool update -force -rename -log teamcity.clearcase.update.result.log
[2009-04-14 14:06:21,642]  DEBUG [Cached pool 3] - .clearcase.ClearCaseConnection - result: ErrCode=1
StdOut:------------
StdErr:------------
cleartool: Error: '/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl' is not a valid snapshot view path.
End----------------

[2009-04-14 14:06:21,658]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 14-April-2009.14:06:21 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl
[2009-04-14 14:06:21,774]  DEBUG [Cached pool 3] - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
StdErr:------------
End----------------

[2009-04-14 14:06:21,775]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 14-April-2009.14:06:11 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl
[2009-04-14 14:06:21,896]  DEBUG [Cached pool 3] - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
StdErr:------------
End----------------

[2009-04-14 14:06:21,896]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - interactive execute: cleartool quit
In vcs.log
[2009-04-14 14:06:10,068]   WARN - ildTriggers.vcs.tfs.TfsSupport - Unable to run Team Foundation Server VcsSupport under non-windows OS
[2009-04-14 14:06:10,090]   WARN - ildTriggers.vcs.vss.VssSupport - Unable to run SourceSafe Support under non-windows OS
[2009-04-14 14:06:21,147]   INFO -      jetbrains.buildServer.VCS - Collecting changes for SDL-TH; from version  14-April-2009.14:06:11; to version  14-April-2009.14:06:21; root=TYPE=BASE
teamcity:vcsRootName=SDL-TH
vcs=clearcase
view-path=/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler

[2009-04-14 14:06:21,155]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool catcs
[2009-04-14 14:06:21,414]  DEBUG - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
element *                                                CHECKEDOUT
# BNS APP (Header files) (test1-4)
element /vobs/product/dxc_ip/xf_delivery/unpacked_files/...  CXCR102007_2-R14A03
# Delivery VOB handling
element -directory /vobs/product/dxc_ip/xf_delivery       /main/LATEST -nocheckout
element -directory /vobs/product/dxc_ip/xf_delivery/...  /main/LATEST
element /vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/...     /main/eto_improvement/LATEST # DCN_H source
element * /main/LATEST
element -directory * /main/LATEST
StdErr:------------
End----------------

[2009-04-14 14:06:21,422]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool update -force -rename -log teamcity.clearcase.update.result.log
[2009-04-14 14:06:21,642]  DEBUG - .clearcase.ClearCaseConnection - result: ErrCode=1
StdOut:------------
StdErr:------------
cleartool: Error: '/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl' is not a valid snapshot view path.
End----------------

[2009-04-14 14:06:21,658]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 14-April-2009.14:06:21 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl
[2009-04-14 14:06:21,774]  DEBUG - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
StdErr:------------
End----------------

[2009-04-14 14:06:21,775]   INFO - .clearcase.ClearCaseConnection - simple execute: cleartool lshistory -all -since 14-April-2009.14:06:11 -fmt %u#--#%Nd#--#%En#--#%m#--#%Vn#--#%o#--#%e#--#%Nc#--#%[activity]p###----###\n /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl
[2009-04-14 14:06:21,896]  DEBUG - .clearcase.ClearCaseConnection - result: ErrCode=0
StdOut:------------
StdErr:------------
End----------------

[2009-04-14 14:06:21,896]   INFO - .clearcase.ClearCaseConnection - interactive execute: cleartool quit
[2009-04-14 14:06:21,912]   INFO -      jetbrains.buildServer.VCS - Finished collecting changes for build configurations [1 - TH SDL (CC)], time spent: 769ms
Seems that a Snapshot view is expected, but I'm trying to connect to a Dynamic view.

Cheers
/om

Hello,

Unfortunately, Maxim who is responsible for ClearCase support will not be available till next week. However, we will try to look into the problem till then.

Am I right that you are listing parts of teamcity-vcs.log and not teamcity-clearcase.log?
Could you please gather the logs I mentioned in my previous comment?
The ones described at http://www.jetbrains.net/confluence/display/TCD4/Reporting+Issues#ReportingIssues-ClearCase

Also, full version of teamcity-vcs log (including full stacktraces, etc.) would be more helpful.


You can attach them to http://jetbrains.net/tracker/issue/TW-7767 or (if you do not want to make them public) send to email or upload to ftp as described in the bollom of the page.

OK, next week is fine.

If you look closely you will see that I have included excerpts with timestamps of interest of:

- the build log
- the clearcase log
- the vcs log

The rest of the logs are timestamped events not relevant to triggering the manual Run.

I think that the item to investigate further is this entry in the CleraCase log:

End----------------

[2009-04-14 14:06:21,422]   INFO [Cached pool 3] - .clearcase.ClearCaseConnection - simple execute: cleartool update -force -rename -log teamcity.clearcase.update.result.log
[2009-04-14 14:06:21,642]  DEBUG [Cached pool 3] - .clearcase.ClearCaseConnection - result: ErrCode=1
StdOut:------------
StdErr:------------
cleartool: Error: '/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl' is not a valid snapshot view path.
End----------------

As I said, I'm connecting to a Dynamiv View, not a snapshot.
Is a snapshot view a requirement?

Cheers

Hello,

Snapshot view is not a requirement, TC must work both with snapshot and dynamic ClearCase views. I will investigate your problem.

Hello,

Please ignore this error, it does not matter. The command "update" for dynamic views generates this error, but TC ignores it.

It seems that you attached only build log and vcs log. Are you really sure that the log above is a part of "teamcity-clearcase.log" file, not the "teamcity-vcs.log" file? If it is not, please attach "teamcity-clearcase.log" file or its part containing timestamps of build #49.

Enclosing the whole logs.
The config spec in question is listed in the clearcase log.
It is a complex config spec, and the elements in question have several branches.

Cheers

Thank you for the provided information.

It seems that your config spec does not contain any load rules, it means that nothing is loaded to your view form the VOB. So the error "Cannot get version in view '/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl' for the directory /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl" seems to be correct. Please add load rule (e.g. "load /vobs") to config spec and try to run build again.

I have never encountered this config spec command before so I quicly googled it:
http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&rs=984&uid=swg21123954
says:

Note: The load rule is NOT part of the syntax for a dynamic view.

I have never used snapshot views, only dynamic ones and all files visible are up to date, always.

Cheers

Thank you for the information, so it is a TC problem. Now I can suggest you a workaround to add "load /vobs" line to your config spec, it will not affect your ClearCase view, but will work in TC.

Adding load rules changed nothing.
Log looks exactly the same. (tried all of load /vobs, load /xf_bns_src and load /vobs/product/dxc_ip/xf_bns_src)
No joy.

Cheers

Did you get the error "Cannot get version in view '/view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl' for the directory /view/etoomr_sdl_view/vobs/product/dxc_ip/xf_bns_src/cnxr10201_1_bns/caxr102007_1_Traffic_handler/sdl" again after adding the load rule?

Yes, exactly!

I'm a bit unsure of the parameter to the load command though.

I have tried:

load /vobs,
load /xf_bns_src and
load /vobs/product/dxc_ip/xf_bns_src

Br.

I fixed two related bugs and attached the patch to the tracker issue: http://jetbrains.net/tracker/issue/TW-7767. Please try it and let me know whether it helps or not.

Tried to overwrite the clearcase.jar 'on the fly', no change. Got the same error.

Then I did:
runAll.sh stop
cp clearcase.jar once more
runAll.sh start

Now I get this yellow banner on the top of the browser page:

Sorry, this patch is not compatible with TC 4.0.2, it is my mistake.

There were many changes in TeamCity ClearCase integration since version 4.0.2 and it is not too easy to write patch compatible with your version. So can you please update your TeamCity to version 4.5 and try this patch again?

OK, running 4.5 now.
Lost my VCS Root setting from 4.0.2 and now I always get this error for the ClearCase view path when testing the connection:

ClearCase view path: *	"/view/etoomr_sdl_view" is not a path to ClearCase view
Relative path within the view: *

I have checked the paths, and they are OK.
What criteria are the view path checked for?

Edit, the VCS Root only seemed lost because I didn't do a browser refresh.
But after Converting to new format (hitting the Convert button in VCS edit form) I still get the same error: not a path to a clearcase view.

Cheers

I noticed that the very first time after the upgrade to 4.5 it worked!
On subsequent runs (after trying to edit the thing) with the obsolete view path settings I get view path errors.

Enclosing the build log.

Oh almost forgot, tried with both original and new clearcase.jar. same result for both, but on the very first run that succeeded the new one was used.

Hello,

I have checked the paths, and they are OK.
What criteria are the view path checked for?

TC runs the command "cleartool pwv -root" that returns the root of the view corresponding to the working directory. What does this command returns in your case?

What does this command returns in your case?

Absolutely nothing.
I only get a new prompt. No output.

Cheers

Starting a new thread on ClearCase in 4.5

Sorry for the delay in replying.
As I know, such behaviour of this command means that the ClearCase view root is exactly in the root of this disk and TC processes this case with this rule.
But in your case this rule is not applicable, so I will think what I can do to solve this problem.