-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Not able to mirror gitlab to github #200
Comments
Hi, |
I had a look and ran into the same issue as you did. Solution for me was to add the source:
gitlab:
# - token_file: /gickup/gitlab-token.txt
# - token_file: gitlab-token.txt
- ssh: false # can be true or false
user: your-username
# username: [email protected]
token: glpat-abczyx
includeorgs:
- myapp
include: # this includes the repo "foobar"
- myapp |
OK so I tried to fill in |
It should be your gitlab username. I just committed code to the |
So this time it got weirder . It did receive the username from
The
If a gitlab has a project , do we include the same in I am not very sure where am I wrong . |
the step "mirrorin myapp to https://github.com" contains the local clone and then the push to Github. Weird that it takes so long, is it a very large repo? The authentication required seems to be coming from github directly. I will do more investigation on that, but I can reproduce the problem. |
If the authentication issue is coming from github ( destination ) I can create a new PAT token and see if it works . I was confused if the authentication failed on gitlab (source) side. |
Ok so I tried with a new token on github and gitlab both tokens does not work for auth still . Yes the repo is on larger side but this time it took around 1minute around . So probably my intermittent internet issue . I suspect the issue is more likely towards gitlab |
I found the error... I didn't add the authentication during the |
Great work !! However one last issue. I am able to work through other smaller repos but this one a pretty heavy one and receiving the message -
Anyway to get around this ? When I clone it on my local it doesn't throw tantrums of course . Here are the logs when I clone it on my local
The downloaded size is arounf 450 MB on disk Looking at docker memory stats I didn't find any spike which might also cause this to fail |
That is a great use case because I don't have such big repositories, so thanks a lot for testing it so extensively. After some digging, I found that someone had a similar issue with |
Went quite far but not quite . I received this error now -
|
damn, this is a hard one. Is gickup able to backup this repo locally? So instead of using |
Thanks for responding so quick . So yes there is absolutely no issue in backing up locally .
The destination config
Docker compose mounted volume
And the zipped file got created |
I pushed a new container on |
Ok so I removed the stale docker container and rerun to pull the new image however the issue remains the same and no information provided too .
|
It comes from the push. Can you check if you have any pre-receive hooks on your repo? |
Which repo ? Github or Gitlab ? On github side the repo was created by gickup so no webhooks are there However on gitlab side there is a sentry webhook . I believe that should not cause any issue as that just listens to gitlab events |
doesn't matter actually. does your repo have a |
You're right . The repo folder indeed does have |
can you check if any of the hooks in there give you issues regarding pushing the code? also try to remove the force parameter from the github push. |
I tried creating one branch and pushing it . It doesn't seem to fail . If thats what you wanted to ask |
destination:
github:
- token_file: /gickup/github-token.txt # alternatively, specify token in a file
# - token_file: github-token.txt # alternatively, specify token in a file
organization: defyjoy
force: false
visibility:
repositories: private # private, public, default: private the other question was if there is actually anything in the hooks directory |
the pre-receive is most likey the culprit |
damn, no all them are just samples, nothing is active... |
Okay so another thing I did is to remove the force parameter from github destination but yet the issue remains the same . |
Few good news I found from another tool .
So there are some huge files which is why it was rejecting for push . But gickup doesn't show this issue. |
Which tool were you using? Maybe I can check what they do differently than me. |
I used this - https://github.com/Enteee/git-sync-mirror |
seems like |
Quick question, is the repository on Gitlab already using LFS? |
I think so . But I am not sure . But I do know that Gitlab is actually storing those huge files . But can't identify which branch right now |
Hi any updates on this. ? |
Not yet. I'll try to do it tomorrow. |
I started working on it. Already had some success, but for now it only pushes your default branch. Also I am not fully happy with the error messages for it. |
can you try to run it on It worked in my tests. I had an LFS repository on Gitlab. Had two branches and mirrored the whole repo to GitHub. |
Hi Sorry for the delay . I will test this and report tomorrow on status for this . |
Did you already test it? |
I will keep you posted tomorrow on this |
Hi, I guess I have a similar problem but the other way around - GitHub to GitLab.
I've noticed that this only happens when syncing LFS-enabled repositories. |
I will run some tests on this and get back to you |
Mind if I ask how large the repository, you try to mirror, is? |
Sure, so I got maybe 10 lfs repos of different sizes, but I would say the smallest is around 1.5 MiB and the biggest around 38 MiB. Thanks for replying. |
@cooperspencer Just wanted to add that my problem seems to be fixed by enabling GitLab mirroring. Previously I was using local checkout+push (for whatever reason).
|
I have tried whatever combination
username
+token
/gickup/gitlab-token.txt
I keep getting error as below . I am not sure what am I doing wrong here
Here is my configuration
Here are the gitlab token permissions -
Here are the error logs -
The text was updated successfully, but these errors were encountered: