How many issue trackers should get this issue?
_Synergy_ is the term used to describe a situation where the final outcome of a system is greater than the sum of its parts.
Integration between different development subsystems does not yield only benefits and efficiency boosts. You can get more issues as well. Here's vivid example:
- User is located in Russia (GMT +5). He sends in the change to SVN at August 1, 01:21 local time (via TSVN 1.5.0)
- Subversion repository (SVN 1.5) is located in the France (GMT +1). It files changes as July 31, 19:21 universal time
- Integration server (CC.NET 1.4) is hosted somewhere in Arizona (GMT -7). A bit later it requests changes in the interval up to July 31, 19:34 universal time (using SVN client 1.5.0.31699)
Subversion server returns XML like:
rinat.abdullin 2008-07-31T17:37:43.265138Z /Platform/trunk/CENSORED.build Restored back FxCop analysis. #DistribRelease rinat.abdullin 2008-07-31T19:21:12.328206Z /Platform/trunk/Libraries/!Readme.txt Note, that the second log entry does not have the msg item. That's what hits CruiseControl.NET hard in some C# code:
private static string ParseMessage(XmlNode logEntry) { XmlNode msgNode = logEntry.SelectSingleNode("msg"); return msgNode.InnerText; }
TortoiseSVN does display the second message properly:

Now here's the challenge: which issue tracker(s) does this issue belong to?
Friday, August 1, 2008 at 2:25
Reader Comments