Hello, this is expected behavior. CCNet just checkout the remote branch, no merging with the local brach is done. If you activate the TagOnSuccess feature ist just commits all changes and create a new tag. And only this tags (all tags) are pushed to the remote repository.
Normally you should have only changes to the AssemblyInfo.cs file or sth like that you dont want to have in your branch comitted. So what is the reason to commit the build changes also to a branch? Daniel Am 30.05.2010 01:50, schrieb wintondeshong: > 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? >
