Commit fba9f34c authored by Robert Speicher's avatar Robert Speicher

Merge branch 'master' into 8-0-stable

parents b907d518 9e139255
Please view this file on the master branch, on stable branches it's out of date. Please view this file on the master branch, on stable branches it's out of date.
v 8.0.1 v 8.0.1
- Improve CI migration process and documentation - Improve CI migration procedure and documentation
v 8.0.0 v 8.0.0
- Fix Markdown links not showing up in dashboard activity feed (Stan Hu) - Fix Markdown links not showing up in dashboard activity feed (Stan Hu)
......
...@@ -474,9 +474,22 @@ Using a self-signed certificate is discouraged but if you must use it follow the ...@@ -474,9 +474,22 @@ Using a self-signed certificate is discouraged but if you must use it follow the
``` ```
1. In the `config.yml` of gitlab-shell set `self_signed_cert` to `true`. 1. In the `config.yml` of gitlab-shell set `self_signed_cert` to `true`.
### Additional Markup Styles ### Enable Reply by email
Apart from the always supported markdown style there are other rich text files that GitLab can display. But you might have to install a dependency to do so. Please see the [github-markup gem readme](https://github.com/gitlabhq/markup#markups) for more information. See the ["Reply by email" documentation](../incoming_email/README.md) for more information on how to set this up.
### LDAP Authentication
You can configure LDAP authentication in `config/gitlab.yml`. Please restart GitLab after editing this file.
### Using Custom Omniauth Providers
See the [omniauth integration document](../integration/omniauth.md)
### Build your projects
GitLab can build your projects. To enable that feature you need GitLab Runners to do that for you.
Checkout the [Gitlab Runner section](https://about.gitlab.com/gitlab-ci/#gitlab-runner) to install it
### Custom Redis Connection ### Custom Redis Connection
...@@ -502,15 +515,6 @@ If you are running SSH on a non-standard port, you must change the GitLab user's ...@@ -502,15 +515,6 @@ If you are running SSH on a non-standard port, you must change the GitLab user's
You also need to change the corresponding options (e.g. `ssh_user`, `ssh_host`, `admin_uri`) in the `config\gitlab.yml` file. You also need to change the corresponding options (e.g. `ssh_user`, `ssh_host`, `admin_uri`) in the `config\gitlab.yml` file.
### LDAP Authentication ### Additional Markup Styles
You can configure LDAP authentication in `config/gitlab.yml`. Please restart GitLab after editing this file.
### Using Custom Omniauth Providers
See the [omniauth integration document](../integration/omniauth.md)
### Build your projects
GitLab can build your projects. To enable that feature you need GitLab Runners to do that for you. Apart from the always supported markdown style there are other rich text files that GitLab can display. But you might have to install a dependency to do so. Please see the [github-markup gem readme](https://github.com/gitlabhq/markup#markups) for more information.
Checkout the [Gitlab Runner section](https://about.gitlab.com/gitlab-ci/#gitlab-runner) to install it
...@@ -6,7 +6,15 @@ You can configure web hooks to listen for specific events like pushes, issues or ...@@ -6,7 +6,15 @@ You can configure web hooks to listen for specific events like pushes, issues or
Web hooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. Web hooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
If you send a web hook to an SSL endpoint [the certificate will not be verified](https://gitlab.com/gitlab-org/gitlab-ce/blob/ccd617e58ea71c42b6b073e692447d0fe3c00be6/app/models/web_hook.rb#L35) since many people use self-signed certificates. ## SSL Verification
By default, the SSL certificate of the webhook endpoint is verified based on
an internal list of Certificate Authorities,
which means the certificate cannot be self-signed.
You can turn this off in the web hook settings in your GitLab projects.
![SSL Verification](ssl.png)
## Push events ## Push events
...@@ -34,7 +42,7 @@ X-Gitlab-Event: Push Hook ...@@ -34,7 +42,7 @@ X-Gitlab-Event: Push Hook
"name": "Diaspora", "name": "Diaspora",
"url": "git@example.com:mike/diasporadiaspora.git", "url": "git@example.com:mike/diasporadiaspora.git",
"description": "", "description": "",
"homepage": "http://example.com/mike/diaspora", "homepage": "http://example.com/mike/diaspora",
"git_http_url":"http://example.com/mike/diaspora.git", "git_http_url":"http://example.com/mike/diaspora.git",
"git_ssh_url":"git@example.com:mike/diaspora.git", "git_ssh_url":"git@example.com:mike/diaspora.git",
"visibility_level":0 "visibility_level":0
...@@ -513,8 +521,8 @@ server.mount_proc '/' do |req, res| ...@@ -513,8 +521,8 @@ server.mount_proc '/' do |req, res|
puts req.body puts req.body
end end
trap 'INT' do trap 'INT' do
server.shutdown server.shutdown
end end
server.start server.start
``` ```
...@@ -529,4 +537,4 @@ When you press 'Test Hook' in GitLab, you should see something like this in the ...@@ -529,4 +537,4 @@ When you press 'Test Hook' in GitLab, you should see something like this in the
{"before":"077a85dd266e6f3573ef7e9ef8ce3343ad659c4e","after":"95cd4a99e93bc4bbabacfa2cd10e6725b1403c60",<SNIP>} {"before":"077a85dd266e6f3573ef7e9ef8ce3343ad659c4e","after":"95cd4a99e93bc4bbabacfa2cd10e6725b1403c60",<SNIP>}
example.com - - [14/May/2014:07:45:26 EDT] "POST / HTTP/1.1" 200 0 example.com - - [14/May/2014:07:45:26 EDT] "POST / HTTP/1.1" 200 0
- -> / - -> /
``` ```
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment