New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitcc label erroring out #75

Open
amousa1968 opened this Issue Dec 12, 2016 · 25 comments

Comments

Projects
None yet
2 participants
@amousa1968

amousa1968 commented Dec 12, 2016

I am using cc2git label
gitcc checkin --cclabel=YOUR_EXISTING_CC_LABEL

getting error
Usage: gitcc [options]
gitcc: error: --cclabel option does not take a value

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 12, 2016

Owner

Yeah, I don't think this was ever actually tested:

42db799

Would need a change to optparse to specify the type as string:

option = {

Owner

charleso commented Dec 12, 2016

Yeah, I don't think this was ever actually tested:

42db799

Would need a change to optparse to specify the type as string:

option = {

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 12, 2016

Can you make the change and I can retest?

amousa1968 commented Dec 12, 2016

Can you make the change and I can retest?

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 12, 2016

Owner

@amousa1968 I'm not going to lie. I haven't used Clearcase (and Python) in almost 10 years. If I thought it would be the last ever change you need to get things working I would be happy to make the change if I got a spare second. But git-cc is definitely not battle-hardened, and this kind of bug is what you can really expect with the whole git-cc experience.

For now I suggest you not use --cclabel and see how far you get. If everything else works fine and want --cclabel then I'll have a quick stab at fixing the bug for you.

Owner

charleso commented Dec 12, 2016

@amousa1968 I'm not going to lie. I haven't used Clearcase (and Python) in almost 10 years. If I thought it would be the last ever change you need to get things working I would be happy to make the change if I got a spare second. But git-cc is definitely not battle-hardened, and this kind of bug is what you can really expect with the whole git-cc experience.

For now I suggest you not use --cclabel and see how far you get. If everything else works fine and want --cclabel then I'll have a quick stab at fixing the bug for you.

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 12, 2016

Owner

Another way of putting it - git-cc is unfortunately/mostly an orphaned project and you really have to be willing to fix or workaround whatever bugs you find. Sorry. :(

Owner

charleso commented Dec 12, 2016

Another way of putting it - git-cc is unfortunately/mostly an orphaned project and you really have to be willing to fix or workaround whatever bugs you find. Sorry. :(

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 12, 2016

Thanks, I'll try it.

amousa1968 commented Dec 12, 2016

Thanks, I'll try it.

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 12, 2016

amousa1968 commented Dec 12, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 12, 2016

Owner

Let me if you could add it to the file since your more familiar with the code.

What happens if you don't specify --cclabel, does git-cc work for you?

Owner

charleso commented Dec 12, 2016

Let me if you could add it to the file since your more familiar with the code.

What happens if you don't specify --cclabel, does git-cc work for you?

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 12, 2016

amousa1968 commented Dec 12, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 12, 2016

Owner

@amousa1968 I don't want to be rude, but I guess this is the kind of extra leg work you're going to need to do to get git-cc working. There is no documentation, it's very bad/old code.

  • I don't know whether python 3.5 is supported, from that error I suspect it is but you have something strange in your configuration or windows path name.
  • What Git remote URL
Owner

charleso commented Dec 12, 2016

@amousa1968 I don't want to be rude, but I guess this is the kind of extra leg work you're going to need to do to get git-cc working. There is no documentation, it's very bad/old code.

  • I don't know whether python 3.5 is supported, from that error I suspect it is but you have something strange in your configuration or windows path name.
  • What Git remote URL
@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 13, 2016

amousa1968 commented Dec 13, 2016

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 21, 2016

amousa1968 commented Dec 21, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 21, 2016

Owner

Hi @amousa1968.

Can you explain this to me where does the .git folder needs to live under to be able to use it properly.

What commands have you run so far? Do you have a separate git repository created by/for git-cc? It will have a .git folder inside it, which is the one you need to look at.

Owner

charleso commented Dec 21, 2016

Hi @amousa1968.

Can you explain this to me where does the .git folder needs to live under to be able to use it properly.

What commands have you run so far? Do you have a separate git repository created by/for git-cc? It will have a .git folder inside it, which is the one you need to look at.

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 21, 2016

amousa1968 commented Dec 21, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 21, 2016

Owner

Did you see the screenshot emailed you earlier?

Github doesn't show images sent from email replies.

.git folder is under git-cc folder.

Um, that's the wrong .git folder. You need to run git init and the other commands in the README in a new folder that's different from git-cc. For example:

C:\git_migration\GitHub\mygitrepository
Owner

charleso commented Dec 21, 2016

Did you see the screenshot emailed you earlier?

Github doesn't show images sent from email replies.

.git folder is under git-cc folder.

Um, that's the wrong .git folder. You need to run git init and the other commands in the README in a new folder that's different from git-cc. For example:

C:\git_migration\GitHub\mygitrepository
@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 21, 2016

amousa1968 commented Dec 21, 2016

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 22, 2016

amousa1968 commented Dec 22, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 22, 2016

Owner

We went through the steps after gitcc update and we skipped gitcc rebase because we're running base clearcase.

update was really added originally as a bootstrap, but it wasn't implemented very well. update calls sync.py, which can you see in this file doesn't look at the Exclude value:

https://github.com/charleso/git-cc/blob/master/git_cc/sync.py#L51

You can see it working here correctly for rebase:

https://github.com/charleso/git-cc/blob/master/git_cc/rebase.py#L215

Not sure what you mean "because we're running base clearcase", what has that got to do with rebase? It was originally written for base clearcase, and should work fine.

Owner

charleso commented Dec 22, 2016

We went through the steps after gitcc update and we skipped gitcc rebase because we're running base clearcase.

update was really added originally as a bootstrap, but it wasn't implemented very well. update calls sync.py, which can you see in this file doesn't look at the Exclude value:

https://github.com/charleso/git-cc/blob/master/git_cc/sync.py#L51

You can see it working here correctly for rebase:

https://github.com/charleso/git-cc/blob/master/git_cc/rebase.py#L215

Not sure what you mean "because we're running base clearcase", what has that got to do with rebase? It was originally written for base clearcase, and should work fine.

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 22, 2016

amousa1968 commented Dec 22, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 22, 2016

Owner

If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help.

Apologies, git-cc rebase is a git-cc command which is poorly named and has nothing to do with UCM rebase. It works equally for both base and UCM. It should have been called pull or something else.

Owner

charleso commented Dec 22, 2016

If your using UCM clearcase then the rebase is recommended but if your using base clearcase you don't need the rebase. Hope this does help.

Apologies, git-cc rebase is a git-cc command which is poorly named and has nothing to do with UCM rebase. It works equally for both base and UCM. It should have been called pull or something else.

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 22, 2016

amousa1968 commented Dec 22, 2016

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 26, 2016

amousa1968 commented Dec 26, 2016

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Dec 27, 2016

Owner

Hi @amousa1968, and Merry Christmas to you too.

As mentioned previously update doesn't respect the Exclude configuration. You can either fix the python code, or alternatively add a .gitignore file to the git repository which should prevent those files being added (much easier).

I'm curious, where does gitcc push come from?

Owner

charleso commented Dec 27, 2016

Hi @amousa1968, and Merry Christmas to you too.

As mentioned previously update doesn't respect the Exclude configuration. You can either fix the python code, or alternatively add a .gitignore file to the git repository which should prevent those files being added (much easier).

I'm curious, where does gitcc push come from?

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Dec 28, 2016

amousa1968 commented Dec 28, 2016

@amousa1968

This comment has been minimized.

Show comment
Hide comment
@amousa1968

amousa1968 Jan 13, 2017

Hi buddy,

I nailed down the gitcc process and the program has been running for 2 days to push 114 labels from clearcase to git, and i tailed the log file to see what is going on and why it is taking time. This is what I found out during the process gitcc update step it is copying files from CC snapshot vob to the gitcc working folder and the copy is taking long long time and it's taking 2 to 3 hours each time while its copying over 7000 to 11000 files. I don't want to modify gitcc update script unless I check with you how do I speed up the process while its executing gitcc update command

amousa1968 commented Jan 13, 2017

Hi buddy,

I nailed down the gitcc process and the program has been running for 2 days to push 114 labels from clearcase to git, and i tailed the log file to see what is going on and why it is taking time. This is what I found out during the process gitcc update step it is copying files from CC snapshot vob to the gitcc working folder and the copy is taking long long time and it's taking 2 to 3 hours each time while its copying over 7000 to 11000 files. I don't want to modify gitcc update script unless I check with you how do I speed up the process while its executing gitcc update command

@charleso

This comment has been minimized.

Show comment
Hide comment
@charleso

charleso Jan 15, 2017

Owner

@amousa1968 As mentioned before the way git-cc was designed to work is to run the rebase command. That uses lshistory to work out what was changed since the last rebase and only add the changes. It's not without problems, but update was really only added to get people started if their initial history was too big/complicated.

Owner

charleso commented Jan 15, 2017

@amousa1968 As mentioned before the way git-cc was designed to work is to run the rebase command. That uses lshistory to work out what was changed since the last rebase and only add the changes. It's not without problems, but update was really only added to get people started if their initial history was too big/complicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment