Cc2SvnBridge ReleaseNotes

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN/CC2HG) Release 4.3

New Features

• Now compatible with Subversion 1.7
• CM-Bridge will now run without a license. However, the number of bridges and update cycles will be limited (5 bridges and 20 update cycles).

Bugfixes

• Fixed a bug when deleting a directory from Mercurial, causing the bridge to not transfer the changes to ClearCase
• CM-Bridge now only counts active bridges towards the license count for Manual Sync (previously, it was any bridge)
• Fixed a few documentation inconsistencies
• Incorrect log messages when merging within Subversion
• Mercurial changes occasionally repeated during subsequent updates
• Properties changes cause multiple revisions in Subversion/Subversion bridges

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN/CC2HG) Release 4.2

New Features

• Remove Subversion Branches created by CM-Bridge during an update
  • CM-Bridge 'private' Branches are removed even when an update fails

Bugfixes

• Changes in Clearcase are incorrectly 'bounced back' from Mercurial/GIT (as an identical check-in)
• Bridge tries to copy changes from a branch other than default/master when bridging ClearCase to Mercurial/GIT
• The Bridge does not send an error email if a bridge is disabled during start-up.
• OVERRIDE_ME Message appears in log file
• Bridge creates a 'dummy' SVN update with no content
  • This issue occurs when updates in CC are performed only by the bridge during an update cycle

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN/CC2HG) Release 4.1

Rebrand Please note that this product has been re-branded from CC2X.

New Features

• Renames in Subversion are now treated as renames within ClearCase (Previously treated as an Add/Remove operation within ClearCase)
• CM-Bridge Web Interface now supports a Subversion repository with no username or password

Bugfixes

• CM-Bridge server can now be started within the CM-Bridge Webadmin Server being started beforehand
• Fixed a bug where the .clearvision_cc2x folder would be transferred into ClearCase
• Improved documentation about upgrading existing CM-Bridge installations

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN/CC2HG) Release 4.0 - Hotfix sr1a

Rebrand Please note that this product has been rebranded from CC2X.

Bugfixes

• Fixed an issue which caused an error in certain circumstances mentioning 'error name logging is not defined'

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN/CC2HG) Release 4.0

Rebrand Please note that this product has been rebranded from CC2X.

New Features

• CM Bridge now bridges with Mercurial
• New CM Bridge license: removes allow svn/git, 1 license fits all

Bugfixes

• Fixed an issue with the log file causing unusual errors when attempting to rollover in windows
• Made bridge data persistant if error on setup
• Tabbed Interface returns to CC2SVN Page on delete bridge
• Fixed a bug with bridges applying the last change twice
• Deleting an Active bridge caused bridge to be suspended not removed
• Fixed an issue with CM Bridge no longer detecting inefficient mode
• Changing User Name and password in web interface did not take effect until restarting CM Bridge server manually
• Manual Sync used to log information for multiple bridges
• Updating multiple bridges at once used to fail
• Fixed an issue where bridge fails in Start Transaction where Change info is None
• Fixed SvnHandler._save_mofidied_changes() incorrectly logging EVERY change not just file/property changes
• When updating SVN, the Successfully transferred data up to revision... message is printed even when no changes occurred

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN) Release 3.0

Rebrand Please note that this product has been rebranded from CC2X.

New Features

• CM Bridge multi-site (allows multiple bridges to be connected)

• Better Support for special Characters in file names

  With GIT Bridges, special Character file names are only supported where the GIT repositories and the bridge reside on the same OS type with the same file encoding (i.e. Windows OS with cp1252 encoding) This is due to the fact that GIT deals with file names as binary sequences and does not allow for OS encoding differences. See https://git.wiki.kernel.org/index.php/GitFaq#Does_git_convert_encodings_of_file_names.3F for more information

• Manually fire a bridge update for an individual bridge
• Adding users to bridge admin (Used for manual updating of bridges)
• Control if Bridge performs an initial synchronisation when starting
  • This will allow bridges to be set up 'as is' without the initial transfer of data (i.e. only newly added files are synchronised)
• Auto creation of Clearvision bridge attributes in ClearCase
• Additional Meta data transferred from ClearCase to Subversion
• Now supports Paths in Git filenames
• Added advanced branching capabilities

Bug Fixes

• Git bridges does not always handle files with spaces
• Some SVN updates can fail if Subversion language is not English
• No validation of install_location setting in config file (causes bridge to fail if incorrectly set)
• ClearCase view needs refreshing before bridge updates to ensure all elements are visible (Linux issue)
• Subversion branch created with backslashes on Linux
• Could not create Subversion branches if the repository had password protection
• Now shut downs cleanly if terminated within a terminal/command line
• SVN Replaces are now caught and dealt with correctly

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN) Release 2.1

This release introduces new functionality to reduce complicated merge conflicts in a Subversion repository

New features

• Subversion side updates are now performed entirely in a 'private' CM Bridge branch.
• A new config option has been introduced to allow control of where CM Bridge should store the branches it creates
  • By default this is in the root of the repository

The CM Bridge (CC2SVN/CC2GIT/SVN2SVN) Release 2.0

This release introduces new functionality for Subversion to Subversion Bridges. In order to to reflect this change in functionality, The ClearCase Bridge product has been renamed to CM Bridge.

This release also addresses some minor issues from Release 1.5.

New Features

• Now compatible with Git 1.6 and 1.7
• Now allows spaces in paths to Git repositories
• New functionality allowing Subversion to Subversion bridges
• All transfers from Subversion are carried out revision-by-revision
• File/folder and revision properties are transferred (on Subversion to Subversion Bridges only)
  • The user can control which properties are not transferred
  • File/folder property conflicts are detected.

Bug Fixes

• Removed spurious spaces when cutting and pasting view paths and repository locations in the web admin interface.
• Unexpected Bridge failures do not bring the entire bridge server down.
• Fixed an issue where occasionally a folder rename/move in subversion would not fully propagate to ClearCase.

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.5

Minor bug-fix release. Fixes include:-

• Resolved issue where under certain circumstances changes from unrelated branches were transferred across the bridge, in particular file deletes.
• Fixed "get_change_set() takes exactly 3 arguments" issue, which occurred for some customers using the 1.4 release.
• Better error reporting for errors in config files.
• Improved merge conflict handling. Now commits the file containing the conflict (including the Subversion diff), making it easier to resolve issues at either end of a ClearCase-Subversion bridge. See User Guide for details on how to resolve Subversion merge conflicts.
• Some ClearCase view errors could cause "time data did not match format" errors to be reported by CC2X for some customers. CC2X has been made more resilient to these problems, which are now logged in the server log file.

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.4

Minor update release to fix a number of issues.

New Features

• For Subversion bridges, support the svn:needs-lock property on files. For files with this property, the CC2SVN bridge will attempt to acquire a lock before applying a change.
• Significant performance improvements for ClearCase repositories with long history.

Bug Fixes

• Support file names starting with hyphens, e.g. afile or file.txt-
• Support elements with hyperlinks on ClearCase side.

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.3

Minor update release to fix a number of issues.

Bug Fixes

• Fix issue with the cc2x_server terminating on merge errors on Linux platforms.
• Fix problem with bridge updates for bridges with trailing slashes in CC repository path
• Allow web admin server to be started from any directory (it was previously required to be started from within the installation directory)
• Table headings in web admin interface becoming obscured when window is sized too narrowly

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.2

Main Features

• First full release of GIT features (CC2GIT).
• Adds bridging of log-messages/comments
• Includes a graphical installer
• First release on Windows XP

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.1

This is recommended update release of the ClearCase Bridge. Please note that CC2GIT functionality is currently in beta with a full release expected soon.

Main Features

• New and improved Webadmin interface including new dialogue for changing passwords and removal of user-name and password from the Git bridge configuration. Subversion and Git bridges have been split into two tables for improved clarity.
• Webadmin interface now only shows options available to the user, e.g. Git related options are only visible if a valid Git-bridge licence is found.
• Now ignores lost+found directories at the top of a bridge on the ClearCase side.
• New option to store a default resolver email address in the config file. This email address is used to seed the Add Bridge form in the Webadmin interface.

Bug Fixes

• Prevent illegal values from appearing in ClearCase side checkpoints. This only affects new bridges and the main symptom is that a new bridge does not transfer ClearCase data until the problem has been resolved.

The ClearCase Bridge (CC2SVN/CC2GIT) Release 1.0

This is the first release of the ClearCase Bridge, introducing bridging functionality between ClearCase on one side and Subversion and/or Git on the other.

Please note that CC2GIT functionality is currently in beta with a full release expected soon.

Main Features

• Automatic bi-directional bridging between ClearCase and Subversion/Git repositories.
• Detection of merge conflicts between repositories with clear conflict-resolution strategies.
• Web-based administration interface.