CLIClientException: Internal error when running rtc2git

[rambaliga]

Hi,

I am trying to run a migration using rtc2git python script and encountering below error,

21:42:44 - Set component 'Dev-ALM_PPM_ADT_Src'(_oVtHEKHBEeKiY-82zS2mKQ) to baseline 'FY18Q4_Aug_Snapshot' (_Bm0L0LEGEei7nNaTvIPLMg)
21:45:09 - Start (re)loading current workspace: scm load -r https:///xxxxxxxxxx.company.com/ccm Target1 --force
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
        at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:782)

I am using an existing workspace which has a single component set to the initial baseline. By using the sh script available under https://github.com/tim-lo/getRTCHistory , I have extracted the changesets for this component. There are 1000+ changesets ,out of which I am trying to migrate only 4-5 changesets.

First of all the changesets are not getting accepted in the workspace. I have set UseAutomaticConflictResolution = True, even then I am prompted to accept the change set.

I have attached the logs for reference. Can you please help and let me know what might be causing this issue? Thanks in advance.

Regards
Ram
log.txt

[WtfJoke]

Hi Ram

Sorry for my late response.

In general if you experience a com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error I cant help you, since that is just a propagated exception from ibm scm cli.

First of all the changesets are not getting accepted in the workspace. I have set UseAutomaticConflictResolution = True, even then I am prompted to accept the change set.

If this is the case, that means that the exit code from the scm cli is not 0 (ok) and indicates that there is some problem which cant be solved with automatic conflict resolution. I need to confess that this is not that obvious that it works that way.

When this happens you can try to load the workspace in eclipse and see if you see any conflicts and try to solve them there. Afterwards you can resume the migration.

I have extracted the changesets for this component. There are 1000+ changesets ,out of which I am trying to migrate only 4-5 changesets.

If you only need to migrate that 4-5 changesets, you probably dont need to go back to the initial baseline.
Can you elaborate a bit more?

I could imagine it would be quite easy to migrate only 4-5 changesets. As long as the changesets happen after each other (Eg. changeset 1 got delivered, then directly afterwards changeset 2... etc).

In this case you would create an rtc workspace where these 4-5 changesets havent been applied. Start the migration and stop after the fifth changeset. You almost could do this by hand, too. 😅

[rambaliga]

Hi Manuel,

Thanks for the response!

For the com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error I have reached out to IBM to get a fix.

If you only need to migrate that 4-5 changesets, you probably dont need to go back to the initial baseline.
Can you elaborate a bit more?

Suppose out of 50 baselines, I want to migrate only few changesets which I am interested in and that starts from say 25th baseline. Can the script handle this? If yes then how can I do it? What should my workspace, config.ini and the history file look like?
The only reason I ask this is we would want to migrate selected change sets which maybe available across different baselines and also more in number, which cannot be migrated manually.

Can you please let me know if this can be achieved with the script?

Thanks.