ClearCase Changes and Continuous Integration
I setup TeamCity on a server. I then created a project and a build configuration.
We are using ClearCase and NAnt. We have the build setup to "Trigger build after a VCS change is detected".
The ClearCase view is using UCM and we are using the snapshot view to build from. If I make a change in ClearCase in another view and deliver, the build never triggers. If we trigger it manually, it says there were no changes but complets the build. Shouldn't the chan ge be picked up and the build be triggered automatically?
Also, should we build off the snapshot view or the integration view?
The debug log for ClearCase is attached below. Any other files needed to help?
Attachment(s):
ccDEBUGlog.txt.zip
Please sign in to leave a comment.
Hi,
Your config spec has selection rules for "ccadmin_1.1.4" branch, but the branch you specified on VCS root settings page is "test_1.1.4" - seems it is the cause of the problem. Try to change your setting to "ccadmin_1.1.4" branch.
Thanks for the reply!!
I changed the branch to ccadmin as requested and I am still having the same issues.
Issues:
1. Builds are not automatically being kicked off when changes are delivered by another user.
2. There are no changes displayed in the changes list (even though there are changes) when a manual build is kicked off.
I attached an updated debug log for ClearCase after the recommended change. I believe that the branch should still be test_1.1.4 rather then ccadmin_1.1.4 because the test stream will contain the changes which need to be found during polling. Users are delivering to the test_1.1.4 branch (the integration stream) and then TeamCity does an update after it detects changes which brings the chanegs down to the ccadmin_1.1.4 branch.
Attachment(s):
newccdebuglog.txt.txt.zip
Ok, can you please now try to not specify any branch (leave "branches" setting field empty) and provide me new debug logs?
I did as you requested. I had the same issues before. The log is attached.
Thansk again!!
Attachment(s):
another.debug.txt.zip
Sorry, but it seems from the log that you used "test_1.1.4" branch at this time, did you? Can you please set "branches" setting to empty string and try again?
I verified, that the branches field is blank in the VCS settings. I did not clear the log before I manually executed the build so it may have a few lines of old data in the front of the file.
I cleaned the log file and retested. The new log file is attached.
Attachment(s):
teamcity-clearcase.log.zip
Well, I found two changes in the log:
But for the "code" subdirectory you have the following rules in config spec:
element "[c09d63bbac4411dd938f0016353e5d08=\vehicleinfosvctest]/code/..." .../ccadmin_1.1.4/LATEST
element "[c09d63bbac4411dd938f0016353e5d08=\vehicleinfosvctest]/code/..." 1.1.4_gdorrell_1ITB0A401_110621_083057 -mkbranch ccadmin_1.1.4
element "[c09d63bbac4411dd938f0016353e5d08=\vehicleinfosvctest]/code/..." /main/0 -mkbranch ccadmin_1.1.4
So the specified changes do not actually affect the content of this view. And seems TeamCity is right in reporting no changes.
As I understand ClearCase behaviour if you want to monitor "test_1.1.4" branch you need a view with config spec like the following:
element * .../test_1.1.4/LATEST
element * /main/0 -mkbranch test_1.1.4
So I would say you should set another view in VCS root settings if you want to see these changes.
That helps, as it answers one of my questions in the first post.
"Should we build off the snapshot view or the integration view?"
I assumed that we are to build off the snapshot view since TeamCity states it does a clearcase update. I moved to a dynamic view (built off the integration stream in the UCM environment) and everything seems to work good now. The build kicked off as it should and the changes were found adn viewable in TeamCity.
Thank you very much for all of your help. It's greatly appreciated!
"Should we build off the snapshot view or the integration view?"
I assumed that we are to build off the snapshot view since TeamCity states it does a clearcase update. I moved to a dynamic view (built off the integration stream in the UCM environment) and everything seems to work good now. The build kicked off as it should and the changes were found and viewable in TeamCity.