Hi Kristis,
I thought I'd give you an update of where I have got to with trying to
close the holes in the Test Director side of ScmBug with regard of
failing to update a given Bug. (I believe the second is a more global
issue for Subversion users)
Our core ScmBug (Based on RELEASE_0-19-17) currently has a patch for:
http://bugzilla.mkgnu.net/show_bug.cgi?id=1015
We then inherit from ScmBug to add some company specific features, and
at this level I have added the fix that I have detailed in:
http://bugzilla.mkgnu.net/show_bug.cgi?id=1014
Between these two changes I believe I've managed to warn the user if
something is going to fail (due to locked or inaccessible bugs) and then
caught any failure on doing a post commit update bug operation.
Both of these fixes are very important for us (which is why I have now
put them on our live system in patch form) as we rely heavily on being
able to track exactly what has been changed under a given Bug. We use
the information as follows:
Auto generate Code Reviews for a given Bug using a set of updates that I
have done to codestriker which I have reported here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1643356&group_i
d=41136&atid=429862
(Other users of ScmBug may find this useful, I have added support for
Subversion and either Bugzilla or Test Director as the tracker, adding
updates for other source control systems shouldn't be too hard if people
wanted to add them)
Also we use this information for merges as we do a reasonable amount of
changes on branches and do specific bug fixes for customers that need
merging into the latest product line. (Although the merges are pretty
much by hand at the moment)
I hope this helps you understand the changes that I've made and why I
have made them.
Thanks
Rob
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
