It's all about the answers!

Ask a question

RTC/Git integration: who's done it/how well does it work?


Paul Smith (26122) | asked Oct 17 '11, 5:30 p.m.
Hi all. I've read the "Integrating other SCM Systems with Rational Team Concert 2.0" document from 2009, which gives a lot of detail but is a little lacking as to the higher-level pros and cons, and searched these forums looking for people who've actually implemented this integration but haven't found much.

Has anyone out there actually implemented the RTC/Git bridge described in the above document? How is it working for you? Do you have any advice? Are you willing to give a general overview of how your system works? With a DVCS there are lots of decisions to make (it seems to me); do you connect RTC with only the "master" git repository? All of them? Etc. Is there any existing community around this environment that I can contact?

What features of RTC does one lose by choosing the Git bridge instead of the builtin SCM? The above doc just says "it is possible to provide a similar type of integration between RTC work items and other SCM systems by using comments and the "Related Artifacts" links provided by the Work Items component. The level of integration will not be as high as with RTC SCM but it is useful none the less"; I'm wondering exactly what "not as high" means: what features are preserved, and which are not.

Finally in some of my readings I've seen discussion of a "connector", while the above doc describes a Git "bridge". Are "connector" and "bridge" different names for the same thing? If not what is the advantage of a connector over a bridge (or vice versa), and if a connector gives tighter integration then is there one available for Git and/or would it be difficult to create one?

Thanks for any guidance/pointers/guidelines anyone can provide!
Cheers!

22 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 26 '11, 12:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Enhancing the GIT integration is being actively investigated, but there
is not yet a committed plan ... stay tuned.

Cheers,
Geoff

On 10/25/2011 11:53 AM, madscientist wrote:
gmclemmwrote:
We use the term "connector" to refer to a mechanism for
integrating two distinct repositories. The terms "bridge",
"synchronizer", and
"importer" refer to different types of connectors. A
bridge allows you to create links from artifacts in one repository to
artifacts in another repository, and allows you to navigate those
links. A synchronizer takes a user-selected object in one
repository, creates a clone of that object in the other repository,
and keeps the object and its clone synchronized. An importer is like
a one-way synchronizer ... taking objects in one repository, and
creating copies in the other repository.
Thanks Geoff; that's very helpful in understanding the docs
available.

So far I've had no responses to anyone using RTC with git, in real
life. Is this not something anyone has ended up doing, "for
real"? The whitepaper is interesting but it was published in
2009 IIRC, and uses RTC 2.0. Are there any updates/enhancements
available if one is using RTC 3.x? I was hoping to find a user
community around RTC+git but so far...

Thanks!

permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 18 '11, 11:27 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
We use the term "connector" to refer to a mechanism for integrating two
distinct repositories. The terms "bridge", "synchronizer", and
"importer" refer to different types of connectors. A bridge allows you
to create links from artifacts in one repository to artifacts in another
repository, and allows you to navigate those links. A synchronizer
takes a user-selected object in one repository, creates a clone of that
object in the other repository, and keeps the object and its clone
synchronized. An importer is like a one-way synchronizer ... taking
objects in one repository, and creating copies in the other repository.

Cheers,
Geoff

On 10/17/2011 5:53 PM, madscientist wrote:
...
Finally in some of my readings I've seen discussion of a
"connector", while the above doc describes a Git
"bridge". Are "connector" and "bridge"
different names for the same thing? If not what is the advantage of a
connector over a bridge (or vice versa), and if a connector gives
tighter integration then is there one available for Git and/or would
it be difficult to create one?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.