It's all about the answers!

Ask a question

Jazz Source Control git Emulation

Kirk Vogen (1271418) | asked Dec 04 '12, 12:39 p.m.

Has it been considered to give Jazz Source Control the ability to emulate a git repository? This would allow one to more easily integrate with external build systems since most support git these days.

Other vendors are going down this path. Perforce can pretend to be a git repository via its Perforce Fusion product. AccuRev can do the same with its Kando. Microsoft Team Foundation Server SCM can emulate a Subversion repository with SvnBridge.

For build systems, a full git emulation wouldn't be needed, just the read operations of the repository.

2 answers

permanent link
Chris McGee (50511117) | answered Dec 06 '12, 4:25 p.m.
There is an article about setting up a full git adapter:

It looks like it requires a full git server in order to replicate changes back and forth.

Kirk Vogen commented Dec 07 '12, 9:40 a.m. | edited Dec 07 '12, 9:40 a.m.

Thank you for the response! I looks like with that solution we'd need to switch over to Git completely. We want to continue to use Jazz Source Control as it works really well for us. It's just that we'd like to integrate with certain external tools that only support the typical SCMs: Git, Subversion, etc. If Jazz Source Control could "pretend" to be a Git repository, than we could use those tools in our software delivery workflow.

permanent link
Steven Wasleski (17633) | answered Dec 21 '12, 11:55 a.m.

As it appears you figured out, the Git adapter Chris refers to is for linking Git commits (or Gerrit changes) and RTC work items. It does not replicate between Git and Jazz Source Control nor does it make Jazz Source Control look like Git.

We are curious to know, however, what specific external tools you are interested in that can not work with Jazz Source Control. Perhaps someone here knows another way to make them work without Git emulation.

Kirk Vogen commented Dec 21 '12, 12:27 p.m. | edited Dec 21 '12, 12:31 p.m.

We are using ThoughtWorks Go to implement a deployment pipeline. That product does not currently have an extension API for implementing support for your own SCMs. It is only compatible with popular SCMs like Git and Subversion. ThoughtWorks is going to be coming out with an SCM extension API, but the API has been delayed significantly. For the time being, we have a Jazz Build Engine (JBE) build that moves changes into a read-only Git repositories as a means of Go integration.

We had been using Jazz Team Build and JBE for building our software. Though that has been fabulous for continuous integration, it doesn't appear to be a good solution for implementing a deployment pipeline, nor does Build Forge. I discussed this a bit in this forum post.

We unfortunately learned too late about IBM SmartCloud Continuous Delivery. That product appears to support the deployment pipeline concept and integrates with RTC.

Michael Dodge commented Dec 28 '12, 3:51 p.m.

Other products fall to this same fate of needing SCM integrations --- Bamboo, SONAR (for additional delta'd insight), the Maven release plugin, and most code review tooling, to name a few.

Would be very curious to get your take on the likelihood of IBM building a facade such as this, versus recommending a path of alternate SCM (such as your Git linkage) to better support these other integrations.

Your answer

Register or to post your answer.