diff options
Diffstat (limited to 'doc/integration/index.md')
| -rw-r--r-- | doc/integration/index.md | 88 |
1 files changed, 30 insertions, 58 deletions
diff --git a/doc/integration/index.md b/doc/integration/index.md index a8aabeefc76..b6cf9013228 100644 --- a/doc/integration/index.md +++ b/doc/integration/index.md @@ -6,54 +6,30 @@ info: To determine the technical writer assigned to the Stage/Group associated w # Integrate with GitLab **(FREE ALL)** -You can integrate GitLab with external services for enhanced functionality. +You can integrate GitLab with external applications for enhanced functionality. -## Services +## Project integrations -Services such as Campfire, Jira, Pivotal Tracker, and Slack -are available as [integrations](../user/project/integrations/index.md). +Applications like Jenkins, Jira, and Slack are available as [project integrations](../user/project/integrations/index.md). ## Issue trackers -You can use an [external issue tracker](external-issue-tracker.md) with the GitLab -issue tracker or use an external issue tracker only. +You can configure an [external issue tracker](external-issue-tracker.md) and use: -## Authentication sources +- The external issue tracker with the GitLab issue tracker +- The external issue tracker only -You can integrate GitLab with the following authentication sources: +## Authentication providers -- Enable the [Auth0 OmniAuth](auth0.md) provider. -- Enable sign-in with [Bitbucket](bitbucket.md) accounts. -- Authenticate with [Kerberos](kerberos.md). -- Enable sign-in with [LDAP](../administration/auth/ldap/index.md). -- Enable creating [OAuth 2.0](oauth_provider.md) applications. -- Use [OmniAuth](omniauth.md) to enable sign-in through: - - Azure - - Bitbucket - - Crowd - - Facebook - - GitHub - - GitLab.com - - Google - - SAML - - Twitter -- Use GitLab as an [OpenID Connect](openid_connect_provider.md) identity provider. -- Authenticate with [Vault](vault.md) through GitLab OpenID Connect. -- Configure GitLab as a [SAML 2.0](saml.md) Service Provider. +You can integrate GitLab with authentication providers like LDAP and SAML. -## Security enhancements +For more information, see [GitLab authentication and authorization](../administration/auth). -You can integrate GitLab with the following security enhancements: +## Security improvements -- [Akismet](akismet.md) to reduce spam. -- Google [reCAPTCHA](recaptcha.md) to verify new users. +Solutions like Akismet and reCAPTCHA are available for spam protection. -GitLab also provides features to improve the security of your own application. -For more details, see [Secure your application](../user/application_security/index.md). - -## Security partners - -You can integrate GitLab with the following security partners: +You can also integrate GitLab with the following security partners: <!-- vale gitlab.Spelling = NO --> @@ -74,37 +50,24 @@ You can integrate GitLab with the following security partners: <!-- vale gitlab.Spelling = YES --> -## Continuous integration - -You can integrate GitLab with the following external services for continuous integration: - -- [Jenkins](jenkins.md) CI. -- [Datadog](datadog.md) to monitor for CI/CD job failures and performance issues. - -## Feature enhancements - -You can integrate GitLab with the following feature enhancements: - -- Add GitLab actions to [Gmail actions buttons](gmail_action_buttons_for_gitlab.md). -- Configure [PlantUML](../administration/integration/plantuml.md) -or [Kroki](../administration/integration/kroki.md) to use diagrams in AsciiDoc and Markdown documents. -- Attach merge requests to [Trello](trello_power_up.md) cards. -- Enable integrated code intelligence powered by [Sourcegraph](sourcegraph.md). -- Add [Elasticsearch](advanced_search/elasticsearch.md) for [advanced search](../user/search/advanced_search.md). +GitLab can check your application for security vulnerabilities. +For more information, see [Secure your application](../user/application_security/secure_your_application.md). ## Troubleshooting +When working with integrations, you might encounter the following issues. + ### SSL certificate errors -When integrating GitLab with services using a self-signed certificate, you might -encounter SSL certificate errors in different parts of the application. +When you use a self-signed certificate to integrate GitLab with external applications, you might +encounter SSL certificate errors in different parts of GitLab. -As a workaround, you can do one of the following: +As a workaround, do one of the following: -- Add the certificate to the OS trusted chain. See: +- Add the certificate to the OS trusted chain. For more information, see: - [Adding trusted root certificates to the server](https://manuals.gfi.com/en/kerio/connect/content/server-configuration/ssl-certificates/adding-trusted-root-certificates-to-the-server-1605.html) - [How do you add a certificate authority (CA) to Ubuntu?](https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu) -- In Omnibus GitLab, add the certificate to the Omnibus trusted chain: +- For installations that use the Linux package, add the certificate to the GitLab trusted chain: 1. [Install the self-signed certificate](https://docs.gitlab.com/omnibus/settings/ssl/index.html#install-custom-public-certificates). 1. Concatenate the self-signed certificate with the GitLab trusted certificate. The self-signed certificate might be overwritten during upgrades. @@ -133,3 +96,12 @@ You can find information in: - `json.exception.class` - `json.exception.message` - `json.message` + +### `Test Failed. Save Anyway` error + +When you configure an integration on an uninitialized repository, the integration might fail with +a `Test Failed. Save Anyway` error. This error occurs because the integration uses push data +to build the test payload when the project does not have push events. + +To resolve this issue, initialize the repository by pushing a test file to the project +and configure the integration again. |