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?
- 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!
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.)
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.)
Comments
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
1 vote
Comments
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Aug 28 '15, 1:21 a.m.1 vote