It's all about the answers!

Ask a question

Jazz features and external SCM integration


Bruno Hondelatte (6) | asked Feb 05 '08, 4:17 a.m.
Hi,

We are trying to see to what extent RTC and TeamServer could be integrated into our current SCM software. In fact, we are using MKS Source, which is a SCM based on rcs version management system.
I have found some pages on integration with Subversion, which seems to handle sources in a quite similar way (I mean, the way is very different, but closer to MKS than the jazz way, which seems closer to ClearCase philosophy).

I understood that there are two ways to integrate with other SCM :
1. importing the current SCM repository into Jazz.net, and then work with rhe Jazz SCM
2. connecting Jazz directly to the existing SCM (as shown on this page : https://jazz.net/wiki/bin/view/Main/SVNAndWorkItems) for example.
We are interested more specifically in the second possibility.
However, the Jazz SCM layer seems to be tightly linked to the continuous integration process (ie. for instance, getting back to the workspace used for the build environment, before fixing errors).
So, in the case we succeed in integrating our SCM to Jazz, as it is done currently with subversion, which Jazz feature may we lose (compared to using native Jazz SCM) ?

2 answers



permanent link
Jean-Michel Lemieux (2.5k11) | answered Feb 05 '08, 6:38 a.m.
JAZZ DEVELOPER
bruno wrote:
Hi,

We are trying to see to what extent RTC and TeamServer could be
integrated into our current SCM software. In fact, we are using MKS
Source, which is a SCM based on rcs version management system.
I have found some pages on integration with Subversion, which seems to
handle sources in a quite similar way (I mean, the way is very
different, but closer to MKS than the jazz way, which seems closer to
ClearCase philosophy).

Jazz is a change-set based SCM system. So compared with base ClearCase
and MKS, yes there are differences. However, Jazz supports the UCM
process and development styles very well, which means that if you know
UCM it shouldn't be a big learning curve.

I understood that there are two ways to integrate with other SCM :
1. importing the current SCM repository into Jazz.net, and then work
with rhe Jazz SCM
2. connecting Jazz directly to the existing SCM (as shown on this page
: https://jazz.net/wiki/bin/view/Main/SVNAndWorkItems) for example.
We are interested more specifically in the second possibility.
However, the Jazz SCM layer seems to be tightly linked to the
continuous integration process (ie. for instance, getting back to the
workspace used for the build environment, before fixing errors).
So, in the case we succeed in integrating our SCM to Jazz, as it is
done currently with subversion, which Jazz feature may we lose
(compared to using native Jazz SCM) ?

You'll basically loose the change-set based SCM support and integrations
we've integrated with work items and build. However, both work items and
builds are extensible and you could potentially extend Jazz with
features from your SCM system, for example, when you run a build you
could attach a MKS tag to the build and provide tooling for reproducing
the build sandbox or allow you to compare builds. But this depends on
the MKS tooling available.

Jean-Michel
Jazz Source Control Team

permanent link
Steven Wasleski (17633) | answered Feb 05 '08, 7:28 a.m.
JAZZ DEVELOPER
bruno wrote:


I understood that there are two ways to integrate with other SCM :
1. importing the current SCM repository into Jazz.net, and then work
with rhe Jazz SCM
2. connecting Jazz directly to the existing SCM (as shown on this page
: https://jazz.net/wiki/bin/view/Main/SVNAndWorkItems) for example.

There is a third option, the connectors framework as described at

https://jazz.net/wiki/bin/view/Main/ConnectorOverview. This is the
framework that underlies the Jazz SCM and ClearCase connectors that are
a part of RTC.

Steve Wasleski
Jazz Jumpstart

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.