Clearvision have released a full bi-directional integration for IBM Rational ClearCase to Git named the CC2GIT Bridge.

The ClearCase Git Integration allows developers to quickly and easily transport code between the two tools, enabling one continuous integrated SCCM environment with the reduced costs associated with open source software.

Looking to Migrate? The CC2Git bridge allows companies to perform a controlled migration within longer timescales, learning and resolving dependencies as they arise, using live data but without impacting on project teams.

Need a Hybrid SCCM environment? Many organisations have IBM Rational ClearCase deeply embedded in their development environment and need to maintain this but wish to leverage the agility and distributed feature set of Git. The CC2Git Bridge provides a multisite solution between IBM Rational ClearCase and Git, providing the best of both worlds.

Read More on our website http://www.clearvision-cm.com/products

Clearvision provide Git Training, Git Support, Git Consulting and Git Products such as our Git Agile Application Lifecycle Management solution UCMGIT.

A new version of Git (v1.6.6.1) has been released, see the release notes below. You can download it from http://git-scm.com/.

This is primarily a fix release.

Git v1.6.6.1 Release Notes (changes since v1.6.6)

• "git blame" did not work well when commit lacked the author name.
• "git branch -a name" wasn't diagnosed as an error.
• "git count-objects" did not handle packfiles that are bigger than 4G on platforms with 32-bit off_t.
• git checkout -m other" while on a branch that does not have any commit segfaulted, instead of failing.
• "git fast-import" choked when fed a tag that do not point at a commit.
• "git grep" finding from work tree files could have fed garbage to the underlying regexec(3).
• "git grep -L" didn't show empty files (they should never match, and they should always appear in -L output as unmatching).
• "git rebase -i" did not abort cleanly if it failed to launch the editor.
• "git reset --hard" did not work correctly when GIT_WORK_TREE environment variable is used to point at the root of the true work tree.
• http-backend was not listed in the command list in the documentation.
• Building on FreeBSD (both 7 and 8) needs OLD_ICONV set in the Makefile
• "git checkout -m some-branch" while on an unborn branch crashed.
• Other minor documentation updates are included.

Clearvision provide Git Training, Git Support, Git Consulting and Git Products including our Git Agile Application Lifecycle Management solution UCMGIT and the ClearCase integration product CC2Git.

If you are running an Apache based Subversion server there are several options available for Subversion Authz:

What is Subversion Authz?

“Authz” is simply jargon that is short for “Authorisation” (similar to “Authn” which is short for “Authentication”). “Subversion Authz” is the method by which Subversion hands out access rights. There are a number of options and if you are deciding to implement a Subversion system.

How does SVN apply Authorization?

When a Subversion client sends information to the server, the user account running the client is identified and the URLs involved in the transaction are made known. As this moment the server can make a decision – should the user be allowed to access this code. If the decision is “yes’ the server calls the Subversion repository management software which can then (optionally) use hooks to check the transaction

Most Companies Use the Fastest Subversion Authorization Solution

Most companies avoid this second authentication step of analysing the transaction itself because it slows the server down. What this means in practice is that read, write, or no access can be allocated based on the URLS used and the user account involved. This is good enough for most purposes but surprisingly the implementation is a bit clunky.

Firstly: many companies wish to tie down both their authentication and authorization to their LDAP systems (or equivalent) so they can use a single sign on mechanism, but there is no seamless way to do this. The two main authorization methods are below.

1. Use Subversion’s mod_authz_svn Apache module to provide authorization. This is good in that the configuration file is clear, easy to manage and quite separate from the Apache configuration files and the server does not need a restart for changes to take affect. However users are defined in groups that are totally unrelated to LDAP –every time a user is moved in or out of an LDAP group you need to synchronize with Subversion. You can of course synchronize the groups in mod_authz_svn’s configuration file using software such as http://python-ldap.sourceforge.net, but this should be native to Subversion.
2. Control the authorization using LDAP groups with native Apache modules to look up LDAP groups and apply protections based solely on URLs. For simple implementations this is fine – but its just too confusing for anything complex. Also you are changing Apaches configuration files so you need to do a graceful server restart each time you alter them, hardly suited to busy corporate environments.

Secondly: It’s hard to grant authenticated write access to a directory, which has a parent with anonymous read access. The solution is to use two different URL locations for Subversion e.g. Send authenticated users through https://dnsname/svn/reposname/, and anonymous users through https://dnsname/svn-anon/reposname/.

Some Companies Need More

We said earlier that most companies avoid the authentication step of analyzing the transaction itself because it slows the server down. However Subversion has a pre-commit hook that allows the transactions to be analyzed prior to a commit. This allows somewhat richer protection e.g.

• read/write/modify permissions for files and/or directories,
• allowing some properties to be change and not others

The script http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/svnperms.py is a freely available hook that helps many companies in this area.

Summary

Subversion provides a number of authentication options but it’s not always simple to apply the best model for your organization.

In addition to Subversion Consulting Clearvision also provide Subversion Training (including Subversion eLearning), Subversion Support and Subversion Products which can help organizations implement an effective, integrated SCCM environment e.g. the Clearvision JIRA Subversion integration and the Agile Application Lifecycle Management (ALM) solution UCM4SVN. Please contact us for more information.

Dates for the 2010 Atlassian Summit have now been confirmed as follows:

Wednesday, June 09, 2010 at 8:00 AM - Friday, June 11, 2010 at 6:00 PM (PT) at the Intercontinental Hotel and Spa in San Francisco.

This is the second Atlassian conference and will cover all Atlassian products including JIRA, Confluence, Crucible, Crown, FishEye, Bamboo and GreenHopper.

The event will highlight the newest and most dazzling plugins, add-ons, integrations, case studies, and features of our entire product portfolio.

Who should come and why:

• Evaluators to get hands-on training and learn from other customers
• Technical teams for best practices using JIRA, Confluence and Atlassian dev tools
• Agile developers for software craftsmanship talks and GreenHopper how-tos
• Project managers for better teamwork, processes, tracking and reporting
• Advanced users that want to build OpenSocial widgets, create plugins, and learn APIs
• Sys admins for managing and tuning Confluence and JIRA deployments
• Plugin developers for learning how to create and market extensions

Clearvision is an official Atlassian partner with customers throughout the world. Clearvision specialise in Atlassian Training, Atlassian User Support, Atlassian Products such as our Subversion JIRA integration (JIRA2SVN) and Atlassian Consulting. Clearvision work with all Atlassian products including JIRA, Confluence, Crucible, Crown, FishEye, Bamboo and GreenHopper.

HgEclipse is a plugin providing support for the highly popular Mercurial distributed version control system within the Eclipse IDE. The Release Candidate of HgEclipse 1.5.0 has been available since November 2009.

The HgEclipse team have announced that the HgEclipse 1.5.0 stable release is available.

HgEclipse 1.5.0 is the first stable release delivered by Intland. Our ultimate goal is to evolve this plugin accompanied by our free and commercial products to a truly Enterprise-scale Distributed Version Control Solution.

You can download the plugin from JavaForge:
http://www.javaforge.com/project/HGE

Changes since 1.5.0RC1:

• New features like "Compare with previous"
• Icon decorations instead of cryptical action letters
• Full set of "Open" and "Compare" context menus for the change set files
• Highlighting the base file in the changed files set
• Consistency fix: default action for double click is now "compare with the previous"
• Tags can be shown for single files
• Sigcheck analysis is optional now
• Graph view bug fixes and performance enhancements
• Merge View improvements:
• Conflict dialog changed from modal dialog to use 3-way merge editor
• New context menus: "Open merge editor", "Open default editor", "Mark resolve/unresolve" and "Show history"
• Ugly text actions from the toolbar removed
• "Compare" action now compares with the predecessor of the current version, if the file is not changed
• Enabled reverting a file (even if file is not changed) to a specific revision from the Revert dialog
• Added content assistance for the "Switch to" revision text field
• New feature to "Close" named branches
• Annotations are following file rename/move history
• Various other bug fixes

The next release is scheduled by 2010 April.

Clearvision are a CodeBeamer specialist providing CodeBeamer licences, CodeBeamer Training, CodeBeamer Support and CodeBeamer related products such as CB2SVN the Clearvision CodeBeamer Subversion Integration.

Clearvision are an open source mercurial SCM specialist providing mercurial training (including mercurial eLearning), mercurial support, mercurial products and mercurial consulting.