No repositories found based on path

[ljhaywar]

The script is executing! Yay! Unfortunately, I'm seeing some errors with the lcsm commands, and the changes aren't being put in my git repo:

I've tried running with and without useProvidedHistory, and I get the same errors either way. I've also tried running with the stream's name instead of UUID. Any ideas on how to fix?

[WtfJoke]

Hmm it looks like the executed lscm command cant find your rtc repo uri/workspace. Can you verifiy if the url is correct by using lscm login -r in the cmd window?

Which rtc version do you use?

[ljhaywar]

I am able to successfully login using
lscm login -r https://hub.jazz.net/ccm11 -u myusername -P mypassword.

The server is Jazz Team Server 5.0.2.

[WtfJoke]

ok thats good. Strange error you get there.... Do you get the same error when you try to run the lscm accept command in the folder where your workspace is loaded?

Some user reported, he needed to extend the accept command by using --target

EDIT: Is the directory located in a strange place or does it contains some special characters?

[ljhaywar]

My Eclispe workspace has all of the changes loaded, so when I run the accept command I'm getting:
Accepting changes:
Workspace unchanged.

I just did some searching, and the script is creating my repository workspace successfully, but there are no files in it.

[WtfJoke]

So according to your description your workspace gets updated, but not the one in the folder.

You could try two things. Start on a not existing workspace.

1. After the first accept of "Sharing project". Can you make a reload of the workspace? (eg. lscm load -r https://hub.jazz.net/ccm11)
2. Specify a target on your accept by adding parameter --target to the accept commands. (eg. lscm accept -v --overwrite-uncommited --target "MYWORKSPACENAME" --changes CHANGES)

One of those should make a change...

EDIT: You started the programm by using useExistingWorkspace=False right?

[ljhaywar]

1. Are you saying to do this while the script is loading?
2. Are you suggesting to modify the script code to have an extra param?
3. I did a little more testing. I've been using a new repo workspace for each script run. In the command line, I ran
   lcsm accept -v --overwite-uncommitted --changes _mylonguuid --target "myGitTestWorkspace13" -r https://hub.jazz.net/ccm11 -u myusername -P mypassword
   The command ran successfully, and when I view the repo workspace files in Eclipse, I can see the changeset in it.

Perhaps I need to modify my version of the script to use --target?

[WtfJoke]

1. Either making a break in the script or doing the steps manually. (But I think its not necessary anymore to do that, since --target seems to help)
2. Yes (should be only one change here on this line: https://github.com/WtfJoke/rtc2git/blob/develop/rtcFunctions.py#L93)
3. Did I get this right. In the folder where your workspace gets loaded there are now changes? Therefore "git status" shows something?

So it really looks like it makes a different in your case. I need to test with my use case.... In my case it wasnt necessary to specify a target.

[ljhaywar]

Thank you so much for your help! I was able to get the script running by making modifications to the Accept command. My changes are in https://github.com/ljhaywar/rtc2git/pull/1/commits. The script is successfully running and saving RTC history to a git repo.

Can you explain how it handles multiple streams? Does each stream translate to a new branch in the same git repository?

[WtfJoke]

Good to hear that it works now. 😄 . I was having a look at your change. Looks good. 👍 Nevertheless I think -r is not required and it should work without it as well (since we login at the beginning of the script).

About multiple streams:
Each stream creates a git branch named after the stream.
The idea is that you run a migration for each stream.

In detail how the script works is like that (just the branching stuff of course):

1. Creates empty git repo (default branch is master)
2. RTC Workspace (created) and loaded
3. Create new git branch (named after rtc stream)
4. Do all the update in rtc workspace and do the same in git
5. Repeat 3. and 4 with all given streams from config file

At the end of the migration you have a master branch (with the initial rtc workspace, which you could throw away) and other branch(es) named after your rtc stream(s). The idea is that you can merge or rebase it afterwards on your own to your master branch.

Since the branches don't conflict (unless two different streams have the same name, but lets assume this isn't possible) it is possible without any problems
So on the same git-repo you could run multiple migrations.

EDIT: I just updated my comment.

[ljhaywar]

Thanks for the info! Your script is going to save us a ton of time!