Import CC version history via CC connector
Preparing for a team to move to RTC from base CC via CC connectior and they want to keep all the version history after the migration.
I read this in the RTC doc:
Does this mean I can't use the Bi-directional synchronization approach if they want to keep all the version history? Or this is just about the version history after the sync has been established?
I read this in the RTC doc:
Important: Do not select Import with history from ClearCase unless you do not need to synchronize changes made in Rational Team Concert source control back to Rational ClearCase. Bi-directional synchronization is not possible when importing with version history.
Does this mean I can't use the Bi-directional synchronization approach if they want to keep all the version history? Or this is just about the version history after the sync has been established?
3 answers
First a clarification: when you select "import from history", that
imports the versions selected by a specified set of labels, not the
entire version history of every element.
WRT that warning, you actually can do bidirectional sync'ing on that
imported history, but it requires some manual steps. In particular:
- Do the "import history sync".
- Create a bi-directional sync stream (with no sync roots).
- In Jazz, deliver the import sync stream to the bi-directional sync stream.
- Do a sync.
- Now you can start adding roots to the bi-directional sync stream, and
it will extend the imported histories with new versions.
Cheers,
Geoff
ghu wrote:
imports the versions selected by a specified set of labels, not the
entire version history of every element.
WRT that warning, you actually can do bidirectional sync'ing on that
imported history, but it requires some manual steps. In particular:
- Do the "import history sync".
- Create a bi-directional sync stream (with no sync roots).
- In Jazz, deliver the import sync stream to the bi-directional sync stream.
- Do a sync.
- Now you can start adding roots to the bi-directional sync stream, and
it will extend the imported histories with new versions.
Cheers,
Geoff
ghu wrote:
Preparing for a team to move to RTC from base CC via CC connectior and
they want to keep all the version history after the migration.
I read this in the RTC doc:
Important: Do not select Import with history from ClearCase unless
you do not need to synchronize changes made in Rational Team Concert
source control back to Rational ClearCase. Bi-directional
synchronization is not possible when importing with version history.
Does this mean I can't use the Bi-directional synchronization approach
if they want to keep all the version history? Or this is just about
the version history after the sync has been established?
First a clarification: when you select "import from history", that
imports the versions selected by a specified set of labels, not the
entire version history of every element.
WRT that warning, you actually can do bidirectional sync'ing on that
imported history, but it requires some manual steps. In particular:
- Do the "import history sync".
- Create a bi-directional sync stream (with no sync roots).
- In Jazz, deliver the import sync stream to the bi-directional sync stream.
- Do a sync.
- Now you can start adding roots to the bi-directional sync stream, and
it will extend the imported histories with new versions.
Cheers,
Geoff
Thanks, Geoff,
So if I want to import full history on every version/element, I can just pick the main/LATEST label and select import from history?
The LATEST (pseudo) label selects at most one version of an element. So
importing LATEST would just import one version, not full history of an
element.
Cheers,
Geoff
ghu wrote:
importing LATEST would just import one version, not full history of an
element.
Cheers,
Geoff
ghu wrote:
First a clarification: when you select "import from
history", that
imports the versions selected by a specified set of labels, not the
entire version history of every element.
WRT that warning, you actually can do bidirectional sync'ing on that
imported history, but it requires some manual steps. In
particular:
- Do the "import history sync".
- Create a bi-directional sync stream (with no sync roots).
- In Jazz, deliver the import sync stream to the bi-directional sync
stream.
- Do a sync.
- Now you can start adding roots to the bi-directional sync stream,
and
it will extend the imported histories with new versions.
Cheers,
Geoff
Thanks, Geoff,
So if I want to import full history on every version/element, I can
just pick the main/LATEST label and select import from history?