-
Notifications
You must be signed in to change notification settings - Fork 32
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
integration of self hosted gitlab not working #236
Comments
same issue here. I followed the migration guide step by step 🤔 |
It looks like that is trying to connect to gitlab.com and not to gitlab.xxxx.de. Did you set the gitlab provider under catalog with host value with the same value in host at integrations? |
The plugin works with self hosted gitlab instance. But it seems that you are not using the processor or that processor is now working correctly. |
Can you post the value of the annotation |
@antoniomuso sure, I will post the value 👍 btw, I have followed section 5 of README.md |
Ok, this is strange, after removing "integrations.gitlab.baseUrl" from the app-config.yaml it is working. after adding it again, it stops working again. I don't see why there is a relationship between these two things.. anyway, just glad that it's finally working. |
Now I am seeing that you have put HTTP for |
you are absolutely right. What a stupid thing for me to do. I tried again with https:https://... and now it works even with the baseUrl set. |
value of |
Can you post your configurations? The processor adds the instance base on |
I can't post the configurations right now but they are almost the same as described by @Santonian . the source location has catalog-info.yaml files that already have gitlab annotation |
What kind of entity are you using for the test? |
I am having a similar issue and had to add |
I have similar issues. I just installed and configured the plugin today with the latest README. There is no mention of Without apiBaseUrl everything crashes with:
After adding apiBaseUrl I'm getting a bunch of
I followed all of the required steps - none of the optional steps. |
I ended up resolving my issue by adding the Thanks everybody who works on this project!! |
Created PR - #319 to update the README. |
This is not the right solution, the code should automatically build the |
In your opinion this is not the right solution...If you have multiple instances you'd have to differentiate them. |
If you post the info regarding your problem, we can find the problem (For example, the requests done in the browser). Because the differentiation of instances is done automatically by code if you use the Backstage GitLab plugin. |
If this is a better solution to automatically annotating based on instances set in configuration, please explain how this is done. It is not apparent by reading through the README. |
The Gitlab Filler Processor does the auto-annotation. If you want to integrate it, follow point .5 of the
|
Thanks! I see the code here. I'll try it out. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
we have self hosted gitlab and I setup the integration like so:
integrations:
gitlab:
- host: gitlab.xxxxx.de
token: MY-TOKEN
apiBaseUrl: https://gitlab.xxxxx.de/api/v4
baseUrl: http:https://gitlab.xxxxx.de
The basic backstage installation cann work with this and can read catalog files from my gitlab repositories.
But the gitlab plugin gives me all kind of 404, when I try to open the gitlab tab of an entity:
... 1] 2023-06-06T08:27:11.419Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415/languages? HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [1] 2023-06-06T08:27:11.445Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415/merge_requests? HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [1] 2023-06-06T08:27:11.468Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415? HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [1] 2023-06-06T08:27:11.668Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415? HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [1] 2023-06-06T08:27:11.674Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415/repository/contributors?sort=desc HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [1] 2023-06-06T08:27:11.679Z backstage info ::ffff:127.0.0.1 - - [06/Jun/2023:08:27:11 +0000] "GET /api/gitlab/gitlab.com/projects/1415? HTTP/1.1" 404 35 "http:https://localhost:3000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" type=incomingRequest [ ...
did I miss something or is the plugin not working with self hosted gitlab installations?
The text was updated successfully, but these errors were encountered: