So the fix of my previous issue with msysgit 1.7 got me further. Now
all builds consistently get triggered via changes to a branch of my
choice, tagging is successful, and pushing of those tags back to the
remote is good. My next, and last problem (so I hope), is with the
pushing of the build modifications. While cruisecontrol is properly
listening to the branch of my choice, in this case "development"
branch, once a build is successful and tagged. It is not pushing the
changes back to the "development" branch but just to a tag out in "Git
Space". So I can find the precise tag, but if I go back to the
development branch it won't contain any of the latest updated version
information or release files. So my question is whether that is
expected and if so...is there is a way around that behavior?
