-
Notifications
You must be signed in to change notification settings - Fork 12
Support self-hosted Gitlab instances #2
Comments
Thanks for the suggestion. This should be fixed in version 0.1.1: you can now specify |
Thanks for the quick response. I have a project that exists both on gitlab.com and a private gitlab instance and my local git repo is configured with two remotes pointing to both of them. I am now running citop 0.1.1 and have both I expected to see both the gitlab.com and private gitlab instance pipelines when running |
It's a restriction that made things simpler but it's not ideal. I've opened #3 on this subject and will look into it:
From your comment I understand that you can successfully monitor the pipelines on multiple GitLab instances (but not at the same time for now) so I will close this issue. Thanks for your help! |
Thank you for implementing so promptly! I'll track #3 |
A number of organizations host their own Gitlab instances rather than use gitlab.com, including both Debian[1] and GNOME[2]. I would like to be able to use
citop
with multiple Gitlab instances.It looks like the gitlab provider code in citop does not support a URL field to map a given gitlab provider/API key to a specific instance of gitlab. I would like to see an addition of such a field, so I could define the following providers in
citop.toml
Using
url
as the field name keeps the definition consistent with the existing implementation in the Travis provider.Let me know if you would prefer this come in as a community contribution, I could have a go at adding support.
[1] https://salsa.debian.org/public
[2] https://gitlab.gnome.org/
The text was updated successfully, but these errors were encountered: