Contents
CodeBeamer2Svn Release 2.1
CodeBeamer2Svn 2.1 is a minor update release, which is fully compatible with the 2.0 release.
New Features
- A config option both client and server side has been added to allow configuration of the timeout period for broken client connections.
Bug Fixes
- Tortoise users can now commit without a Subversion comment again.
CodeBeamer2Svn Release 2.0
![/!\](img/alert.png "/!\"){kind=small}
Please note that CodeBeamer2Svn 2.0 is incompatible with previous releases. Server, Subversion hooks and all clients must be upgraded at the same time.
Main Features
Detect Broken Client-Server Connections
CodeBeamer2Svn can now detect broken connections between a client and the server. When a connection breaks, both server and client will detect this independently and drop the connection cleanly. Connections can break for a variety of reasons. Common reasons are:-
- The client machine's IP addresses changes, e.g. because of a client switching between wired and wireless networks or because of VPN (Virtual Private Network) connections being opened and closed.
- Network equipment between client and server stops working or is unplugged.
- A broken network connection either at the client or the server end.
- Network cables being unplugged.
In previous releases a broken connection could cause Subversion commits to hang (with one of the symptoms being a Subversion hook on the Subversion server being left behind). Such broken connections are now detected early and tidied up. Any hanging commits are terminated with an error message.
Other New Features
CB2SVN can now handle very large lists of tracker items returned from CodeBeamer reports. In previous releases this could cause problems with network communication resulting in clients being disconnected unexpectedly.
- CB2SVN now supports special and foreign-language characters in Subversion log messages.
CodeBeamer2Svn Release 1.0
First release of CodeBeamer2SVN, providing improved integration of CodeBeamer with Subversion.
Main Features
- Graphical user interface that allows users to choose from list of available tracker items on commit.
- Allow administrators to enforce process policies such as requiring tracker item ids with every commit.
- Allow users to move tracker items to their next state on commit.