The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Foundations |
| Maturity | Viable |
| Content Last Reviewed | 2024-04-22 |
Thanks for visiting this category direction page on Integrations in GitLab. This page belongs to the Import and Integrate group of the Foundations stage and is maintained by the group's Product Manager, Magdalena Frankiewicz (E-mail, Calendly).
This direction page is a work in progress, and everyone can contribute:
GitLab's vision is to be the best single application for every part of the DevOps toolchain. However, we acknowledge that to achieve this, there are many workflows, custom scripts, and nuanced integrations that customers require and GitLab may not be able to prioritize.
To make the most impact and keep the Integrations category sustainable, we will focus on improvements to the technical foundations of integrations as well as documentation, guides, and best practices to assist the broader community in contributing to integrations.
As we continue to scale how we support integrations at GitLab, we are working closely with product teams to shift support and prioritization to the relevant areas of the product. Similar to APIs, webhooks, audit events, authentication, and other horizontal services, integrations are better supported by the teams closest to the source of customer pain and need. Rather than centralized prioritization, this enables teams to think outside of the box about how integrations can take their features to the next level, gain more exposure from new audiences, or integrate strategically with competitors to achieve business outcomes.
To support teams in building integrations, we'll be focusing on the technology and tools product teams will leverage to build integrations, including our APIs, webhooks, our Static Integrations DSL, and further abstractions to simplify the process of building integrations.
To achieve this we'll be focusing on the following areas:
Considering Integrations domain, so far in 2024 we worked on:
From May 2024 we discontinue working on Jira integrations, so that we can instead focus on developing Jira importer.
We will continue improving the GitLab for Slack app at a slow pace.
GitLab does not utilize a plugin model for integrations with other common tools and services, or provide a marketplace for them. As an open core project, integrations can live directly inside the product. Learn more about our reasons for this in our Product Handbook.
This does not mean we will never build a "marketplace" for GitLab, it just means we have no intention of doing it at this time.
Import and Integrate group won't focus on developing new integrations, but we will continue to support other GitLab product groups, partners and Community contributors in doing that.
We'll continue to support core functionality for cross-stage integrations, primarily "notification" integrations, such as Slack or Google Chat. Cross-functional teams, however, will be responsible for building new domain-specific integration features that apply to their particular product group or stage.
We are working to shift responsibilities as DRIs of integrations to individual product teams within the domain areas across GitLab. This will give groups full visibility and ownership in serving customers in their domains, based on group's comprehensive strategy. This will also help to make Integration category more sustainable. We want more integrations to be added over time, and sharing the ownership of these with other groups makes this possible and scalable.
Group Import and Integrate keeps ownership of the foundations of integrations and the Integration development guidelines. We keep offering guidance on integrations best practices to anyone that contribute.
As we work to better define ownership of integrations across GitLab, the list below clarifies the current ownership of maintenance, security, and new feature development of each integration.
Security related integrations, owned by group Anti-Abuse:
CI/CD integrations, owned by group Pipeline Execution:
Integrations owned by group Project Management:
Integrations owned by group Source Code:
Integrations owned by group Incubation:
Elasticsearch integration is owned by group Global Search.
Datadog integration is owned by group Runner.
Gitpod integration is owned by group IDE.
Harbor integration is owned by group Container Registry.
Packagist is owned by group Package Registry.
Visual Studio Code extension is owned by group Editor Extensions.
External issue trackers, ownership negotiated with group Project Management, currently maintained by group Import and Integrate:
"Notification" integrations, maintained by group Import and Integrate:
Other integrations, currently maintained by group Import and Integrate:
If you want to contribute to an existing integrations, you can look for open issues labelled with this integration name, e.g "Integration::Asana" or "Integration::Jira".
If you'd like to contribute a new integration, please first review Integration development guidelines. Contact GitLab group owning the domain the new integration fits best, so that the group is aware of the planned contribution. Import and Integrate offers guidance on integrations best practices during development, by reviewing MRs and answering technical questions.
If you're interested in general Integrations area, you can find open issues with ~"Category:Integrations" label, however this list contains issues specific to particular integrations as well.
Feel free to reach out to the team directly if you need guidance or want feedback on your work by using the ~"group::import and integrate" label on your open merge requests.
You can read more about our general contribution guidelines here.
If your company is interested in partnering with GitLab, check out the GitLab Partner Program page for more info.