Hi Jerome. The CCASE GIT connector is not bi-directional, and is intended only to integrate work done in a Git repository into ClearCase upon a commit or push, as configured.
Really? In the documentation you'll find this : This document describes how to install, configure, and use HCL's ClearCase Git Connector in your own environment. With ClearCase Git Connector, you can copy and sync the content and history of a Git repository to a corresponding ClearCase VOB ("Git-to-CC"), or conversely copy and sync everything from a ClearCase VOB to a Git repository ("CC-to-Git") So it is possible to copy from ccase to git according to the UserGuide ... and I have find script to do that and a procedure to install and configure those script (CC-to-Git) So i'am a bit confused ...
Find below the describe of CC-To-Git tools [CC-to-Git](//muut.com/u/clearcase-clearquest-community/s1/:clearcase-clearquest-community:WU5i:cctogit.png.jpg)
Jerome, we think you must have an earlier preview version. We dropped that functionality in the subsequent, supported version. Could you elaborate on what you're trying to do?
I have the version I found with my passwport advantage, and nowhere it is explained that cc-to-git it will be not supported in other future versions. However I need to copy only a few vob of my vob server to git for a particular project where the scm will be GIT. We need for that to keep the full hystory of vob and copy it into git repos. When reading the CCASE GIT CONNECTOR UserGuide it is explained that the script cc-to-git should work like this but unfortunately I have somme issues with this tools. And when I ask for IBM/HCL support they told me that this not possible to make cc-to-git but only git-to-cc. So can you bring me your support in this way? Jerome
I think you probably have a preview version of the software that was made available through PA. The CC to Git piece was never really finished, and we decided that we did not want to support this aspect of the connector. In addition to the difficult technical aspects of providing such a feature, I think you can imagine what the business-related considerations were that informed the decision to support only Git to ClearCase synchronization. I'm curious as to why the developers that need to work on this project are unable to use ClearCase to do so. Could you elaborate? If the issue is that they know Git, but do not know ClearCase, one enhancement we are considering in the future is a Git-like front end to ClearCase. We are also considering whether to enhance the MVFS and our build tools to allow build-auditing and build-avoidance to work with assets in other SCMs, like Git. Would either of these be of interest to you? Thanks, Howie