Understanding Global Configuration Management with a Git SCM
I would like to understand what features/functions in RTC 6.0 or 6.0.1 are lost or impacted when Git is used as the SCM component rather than RTC. Scanning the high level features of GCM, are any of these areas limited or no longer functional if using the Git Interface?
I've been unable to find any clear reference work on GCM using Git. Can anyone point me to more information? Thanks in advance! |
Accepted answer
Hi Shawn, you are right -- we added support for Global Configurations in RTC 6.0.
You can link a Global Configuration with an RTC baseline, stream, or snapshot. This will let you manage global configurations that include all of the artifacts that make up a development project, including requirements, designs, test artifacts, and source code. There is no Git extension to support the OSLC Configuration Management spec, so it's not possible to link Git source code into a Global Configuration. It is possible that someone will write one eventually (possibly even IBM) but we have no plans at this point. So in summary, right now Git does not support any of the scenarios you listed. (RTC SCM does not support all of them yet, but it is in our roadmap.) Geoffrey Clemm selected this answer as the correct answer
Comments Adding to Darcy's answer...
Geoffrey Clemm
commented Dec 15 '17, 3:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
While Daniel's comments are all true, to avoid any misunderstanding, Daniel is describing integrations between git and RTC work items, not integrations between git and global configurations. As of this date (Dec 2017) there is no integration provided by IBM between git and global configurations. Note that because the integration with global configurations is defined by an OSLC interface, any third party could implement such an integration ... it does not have to be provided by IBM. |
One other answer
You can use GIT with Global configuration. There should be no issues. Please notice that Global Configuration is not implemented yet in RTC so there is no impact on the behavior in RTC (no matter if integrated with GIT or not).
Comments Thanks for the answer! How does versioning work in this environment (GCM with Git SCM). Is there any impact in this area?
Krzysztof Kaźmierczyk
commented Aug 25 '15, 8:37 a.m.
See my answer above. Global Configuration does not work in RTC yet so there is no impact (positive or negative) on RTC or GIT.
Looking at the product page here, it seems GCM is a released part of 6.0 (although there are important features also coming out in 6.0.1 in this area). Could you elaborate?
With respect to the comment from Krzysztof Kaźmierczyk, are there any articles or whitepapers which talks about integration of GC with GIT?
1
Geoffrey Clemm
commented Dec 15 '17, 3:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that Darcy's answer is the correct one. In 6.0, you can contribute RTC streams and snapshots to global configurations. In the releases since then, significant additional functionality has been added to this integration. For example, you can create links between RTC files and other RTC files, RQM artifacts, and DNG artifacts, and can navigate those links in a Global Configuration context. As of this date (December 2017) IBM provides no integration between git and global configurations, but such an integration could be written by a third party ... it would not have to be written by IBM. |
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.
Comments
Note that a "component" is normally not used to create a work context, unless you are a strictly component-based development shop, where a given developer always works on exactly one component. A work item is usually what is used to create a work context.