-
Notifications
You must be signed in to change notification settings - Fork 106
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
custom gitlab still no syncing #165
Comments
Next things you can check:
|
hit:
52 Buddy\Repman\Message\Organization\SynchronizePackage 2020-05-19 20:46:11 Too few arguments to function Buddy\Repman\Service\PackageSynchronizer\ComposerPackageSynchronizer::__construct(), 4 passed in /var/www/repman/var/cache/local/ContainerX8StnRW/Buddy_Repman_KernelLocalContainer.php on line 1690 and exactly 5 expected
|
Looks like you need to clear cache ( Next you can run: Tip: if you do manual update please check
(it is for now, but it can always change) |
now it fails with Error: No driver found to handle VCS repository https://somegitlab.tld:8888/mygroup/myproject |
What is the type of package? Because authorization for this type of files is set only for packages added by the oauth integration. Otherwise, you need to either add the repman's ssh key to your gitlab instance and use the git repository link, or use the token link as you wrote earlier. |
oauth ( clicking through → organization → add package → gitlab → "repository/path" ) |
So this might be related, but when I use a custom GitLab host and add a repository, I get that the Screenshot of the messenger:consume with My guess: the |
Did some debugging and it turns out Composer uses the First of all I think the last two arguments of https://github.com/repman-io/repman/blob/master/src/Service/PackageSynchronizer/ComposerPackageSynchronizer.php#L121 need to be swapped? Although Composer itself in their Gitlab driver also uses this order 🤔 . But even with that it doesn't work. Composer uses the GitDriver to fetch the data. I tried updating |
Hi @nickygerritsen, is this on your local machine? Would you try reproducing that using docker? |
It is on my machine with a clone from master without Docker. |
Sure, just create version: '3.4'
services:
app:
image: repman:beta
build: .
consumer:
image: repman:beta
build: .
cron:
image: repman:beta
build: . And run although you could start with removing your GitLab token (Profile -> Unlink GitLab) and trying again? |
Just tried Docker, that gives the same issue indeed. |
See the PR I just created, that seems to fix it for me at least. |
@bash-stack please try to update (#179) and check if this fix helps |
@bash-stack do you think we can close this issue now? |
#158 followup ...
the first entry is https://username:token , worked ,
custom gitlab entries get stuck ( and yes
bin/console messenger:consume async
is running )Logs:
The text was updated successfully, but these errors were encountered: