Commit 26544eab authored by Job van der Voort's avatar Job van der Voort 🚀
Browse files

Merge branch 'gmail_actions_doc' into 'master' 

Add Gmail actions button for GitLab doc.

Resolves #1517 by adding doc with some notes.

See merge request !1327
parents a6f2caf7 4e33b47a

doc/integration/README.md

+1 −1
Original line number Diff line number Diff line
@@ -10,7 +10,7 @@ See the documentation below for details on how to configure these services. 
- [SAML](saml.md) Configure GitLab as a SAML 2.0 Service Provider

- [Slack](slack.md) Integrate with the Slack chat service

- [OAuth2 provider](oauth_provider.md) OAuth2 application creation

- [Gmail](gitlab_buttons_in_gmail.md) Adds GitLab actions to messages

- [Gmail actions buttons](gmail_action_buttons_for_gitlab.md) Adds GitLab actions to messages



GitLab Enterprise Edition contains [advanced JIRA support](http://doc.gitlab.com/ee/integration/jira.html) and [advanced Jenkins support](http://doc.gitlab.com/ee/integration/jenkins.html).

doc/integration/gmail_action_buttons_for_gitlab.md

0 → 100644
+22 −0
Original line number Diff line number Diff line 
# Gmail actions buttons for GitLab



GitLab supports [Google actions in email](https://developers.google.com/gmail/markup/actions/actions-overview).



If correctly setup, emails that require an action will be marked in Gmail.



![gmail_actions_button.png](gmail_actions_button.png)



To get this functioning, you need to be registered with Google.

[See how to register with Google in this document.](https://developers.google.com/gmail/markup/registering-with-google)



*This process has a lot of steps so make sure that you fulfill all requirements set by Google.*

*Your application will be rejected by Google if you fail to do so.*



Pay close attention to:



* Email account used by GitLab to send notification emails needs to have "Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least".

* "A very very low rate of spam complaints from users."

* Emails must be authenticated via DKIM or SPF

* Before sending the final form("Gmail Schema Whitelist Request"), you must send a real email from your production server. This means that you will have to find a way to send this email from the email address you are registering. You can do this by, for example, forwarding the real email from the email address you are registering or going into the rails console on the GitLab server and triggering the email sending from there.



You can check how it looks going through all the steps laid out in the "Registering with Google" doc in [this GitLab.com issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/1517).

doc/integration/gmail_actions_button.png

0 → 100644
+16.9 KiB
Loading image diff...