- Type:
- Bug
- Priority:
-
Critical
- State:
- Fixed
- Subsystem:
- Version Control
- Reporter:
- Stefan Burwitz (burwitzs)
- Assignee:
- Olesya Smirnova (lesya)
- Affects:
- Teamcity 3.0 (Benares, 5985)
- Fixed in:
- TeamCity 3.1 (6760)
- Created:
- 9 months ago (23 Jan 2008 18:41)
- Updated:
- 9 months ago (12 Feb 2008 12:58)
- Votes:
- 0
- Resolved:
- —
- JIRA source:
- TW-4308
We have a number of projects configured. Occasionally a CVS commit to one module will result in TeamCity VSC picking up the change in a different module triggering a build for the other module. The module on which the commit was made never sees the update in TeamCity. We have to force a build which it then gets latest and is built fine.
This has happened at least six times in the last three weeks and affects our release cycle. Please advise on when we might get a fix for this problem.
The module files in question have the following CVS paths:
The file NetworkElements/CIM/Service/CIMSqlServerDataAccess.cs was modified which falls under project bs.cim with checkout rule NetworkElements/CIM. However the project bs.civ was built and indicated the change NetworkElements/CIV/Service/CIMSqlServerDataAccess.cs - this file does not exist under the CIV module. Please see attached screen dump.
Environment: Windows Server 2003
Issue wasresolved
| Old | New | |
| Stefan Burwitz (burwitzs) - 9 months ago (12 Feb 2008 12:58) | ||
| Fixed in version | Benares Minor (3.1) | |
| Fixed in version | TeamCity 3.1 (6760) | |
Stefan Burwitz (burwitzs)
9 months ago (23 Jan 2008 18:50)Screenshot shows file checked out against the wrong module.
Olesya Smirnova (lesya)
9 months ago (05 Feb 2008 21:15)Stefan, how many configurations use this root? Could you list all checkout rules configured for the root?
Do you use cvs modules? Do you use "history enabled" option?
Could you attach cvs log for the file (NetworkElements/CIM/Service/CIMSqlServerDataAccess.cs)? Is there the corresponding file in the ".cim" project (NetworkElements/CIV/Service/CIMSqlServerDataAccess.cs)? Could you attach its log also?
Thanks!
Stefan Burwitz (burwitzs)
9 months ago (06 Feb 2008 08:50)About 74 projects share the VCS root. Do you really want me to list all the checkout rules for all of these projects?
Check out rule for CIM: +:NetworkElements/CIM
Check out rule for CIV : +:NetworkElements/CIV
We use CVS and we don't use the history enabled option.
I will attach the CIM and CIV project logs shortly.
The file NetworkElements/CIV/Service/CIMSqlServerDataAccess.cs) does not exist in CVS.
Olesya Smirnova (lesya)
9 months ago (06 Feb 2008 16:44)No, thanks!
Do they look the same as described one (NetworkElements/${some module name})?
Is the file CIMSqlServerDataAccess.cs change always displayed in the wrong project if it is changed?
Stefan Burwitz (burwitzs)
9 months ago (08 Feb 2008 10:40)All of our checkout rules take the form +:${parent dir}/${module name}.
The SIMSqlServerDataAccess.cs file does not always display in or trigger the wrong project.
Which logs do you require?
Olesya Smirnova (lesya)
9 months ago (08 Feb 2008 13:13)I asked for "cvs log" for the file, but if the problem is not stable reproducible it is just useless... Thanks for the help, I'll try to reproduce it myself
Stefan Burwitz (burwitzs)
9 months ago (08 Feb 2008 13:19)The buildagent teamcity-vcs.log is empty. We are using checkout on agent option under VCS settings.