It's all about the answers!

Ask a question

Understanding Global Configuration Management with a Git SCM

Shawn Pease (3123) | asked Aug 24 '15, 9:25 a.m.

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?

  • Configuration use case management across context for RM, QM, CM
  • Work in parallel on multiple releases
  • Reconstitute a dev environment from a past release
  • Compare across configurations and deliver to another stream
  • Branch to create a new release or product variant
  • Express a product/app as a set of components (hierarchy) and reuse components in multiple variants (product lines)
  • View an entire global configuration hierarch in a single tree view
  • Create a component to establish a work context
  • Create a stream to group configurations from any CLM tool
  • Add, replace, duplicate and remove configurations from a stream
  • Create baselines of configurations to save milestones at critical release points
  • Find configurations where a stream or baseline is used

I've been unable to find any clear reference work on GCM using Git.  Can anyone point me to more information?

Thanks in advance!

Geoffrey Clemm commented Aug 28 '15, 1:21 a.m.

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.

Accepted answer

permanent link
Darcy Wiborg-Weber (1012) | answered Aug 26 '15, 3:18 p.m.
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

Daniel Moul commented Aug 26 '15, 5:09 p.m.

Adding to Darcy's answer...

While this falls short of the use cases listed in the original post, using Jazz work items it is possible to indirectly associate git commits with other lifecycle artifacts that are in global configurations.

  1. You can use global configurations with requirements, designs and test cases.
  2. In the work item system you can associate releases and other "deliverable" attributes with global configurations.
  3. You can create plans for the releases mentioned in (2).
  4. You can create implementation plan items in those plans as well as defects etc that are "found in" or "planned for" the releases mentioned in (2)
  5. You can use the RTC-git integration to associate those work items with git commits.

Geoffrey Clemm commented Dec 15 '17, 3:11 p.m.

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

permanent link
Krzysztof Kaźmierczyk (7.5k480103) | answered Aug 24 '15, 9:31 a.m.
edited Aug 25 '15, 8:36 a.m.
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).

Shawn Pease commented Aug 25 '15, 8:28 a.m. | edited Aug 25 '15, 8:35 a.m.

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.

Shawn Pease commented Aug 26 '15, 2:14 p.m. | edited Aug 28 '15, 1:15 a.m.

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?

Radha Nagaraja commented Dec 14 '17, 9:10 a.m. | edited Dec 15 '17, 3:04 p.m.

With respect to the comment from Krzysztof Kaźmierczyk, are there any articles or whitepapers which talks about integration of GC with GIT?

Geoffrey Clemm commented Dec 15 '17, 3:18 p.m.

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

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.