Bug 1931517 - Add a gitlab connector
Summary: Add a gitlab connector
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Extensions
Version: 5.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-22 15:44 UTC by Till Maas
Modified: 2025-10-16 23:58 UTC (History)
0 users

Fixed In Version: 5.0.4-rh55
Clone Of:
Environment:
Last Closed: 2021-04-29 00:17:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure Red-Hat-Bugzilla/rh-bugzilla pull-request 1# 0 None None None 2021-04-07 06:19:15 UTC

Description Till Maas 2021-02-22 15:44:30 UTC
Description of problem:


https://bugzilla.redhat.com/show_bug.cgi?id=1657069 contains links to merge requests on freedeskopt gitlab such as https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/738 

The status of that link shows only None for Status or Summary. It would be great if it would show the actual summary or merge request status like it is done for GitHub.

Comment 1 Jeff Fearn 🐞 2021-02-23 04:45:13 UTC
There isn't a connector for GitLab ATM.

If you want to sync the data yourself you can do so using the API.

https://bugzilla.redhat.com/docs/en/html/integrating/api/Bugzilla/Extension/ExternalBugs/WebService.html#update-external-bug

Note that we do not use authentication with external services, so a connector once added would be limited by any site polices for unauthenticated API usage.

Comment 2 Jeff Fearn 🐞 2021-04-07 06:30:10 UTC
Pulled the PR in to the internal git repo, but due to how that whole thing works it means I had to close the PR.

Comment 6 Jeff Fearn 🐞 2021-04-28 01:11:31 UTC
This fix has been deployed to https://partner-bugzilla.redhat.com for public testing.

Comment 7 Jeff Fearn 🐞 2021-04-29 00:17:49 UTC
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.


Note You need to log in before you can comment on or make changes to this bug.