Skip to content
Snippets Groups Projects

Release 8.6.0

Merged Rémy Coutable requested to merge release-8-6 into master
1 file
+ 50
1
Compare changes
  • Side-by-side
  • Inline
@@ -9,7 +9,15 @@ author_twitter: Jobvo
image_title: /images/7_X/PICTURE.PNG
---
Intro and introduce main features here.
Never have there been more people contributing to GitLab. And you can see it.
Whether you're leading a large open source project or thousands of private,
interlinked projects, with GitLab 8.6 your life is going to get a whole lot
easier.
Not only can you now effortlessly deploy to Kubernetes with GitLab Deploy,
it's now so much easier to only get the messages you need with
the ability to subscribe to labels. And even if you don't care about those
things, we made everything faster and _feel_ better.
This month's Most Valuable Person ([MVP](https://about.gitlab.com/mvp/)) is
Marcia Ramos for helping us [improving GitLab Pages documentation][gl-pages]
@@ -19,19 +27,42 @@ necessarily mean contributing code to GitLab!
Thanks Marcia!
[gl-pages]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/212
[dear-github-response]: https://about.gitlab.com/2016/01/15/making-gitlab-better-for-large-open-source-projects/
<!--more-->
## GitLab Deploy
GitLab has always been the place where your projects start their life,
where you collaborate in issues and diffs and even test your code.
Now, GitLab is also the place where you ship you code quickly and easily
to Kubernetes.
EXPLAIN WHAT IT DOES
> [Documentation link](link)
## Subscribe to a Label
If you don't want to miss issues that are important to you, simply
subscribe to a label! You'll get notified whenever the label gets added to
an issue, making sure you don't miss a thing.
> [Documentation link](link)
## Confidential Issues
At GitLab [we're all about being open][open], but you can't share everything.
For sensitive subjects, you can now make a confidential issue in a project.
This issue will only be visible to the members of the project and the creator of
the issue, even if the project is public or internal.
This means people can now safely report security issues to your open source
projects. You can communicate with them right there and then, without having
to rely on external applications.
[open]: https://about.gitlab.com/2015/08/03/almost-everything-we-do-is-now-open/
> [Documentation link](link)
## External Users
@@ -50,6 +81,8 @@ Thanks Marcia!
> [Documentation link](link)
## Move issue to another project
## Performance improvements
* Search performance has been greatly improved for users using PostgreSQL
@@ -65,6 +98,20 @@ faster and is cached
* The branch commit ahead/behind statistics are no longer pre-cached on every push. For projects with lots of branches (e.g. thousands) this can have a huge impact on the time it takes for the pre-caching process to complete. Merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3274
* Indexes were added for `ci_runners.token` (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3249) and `git_hooks.project_id` (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/271)
- performance of viewing individual issues will be improved by caching certain Git operations
- We enabled HTTP caching for requests that fetch the raw contents on a single
file in a Git repository. Cache times range from 1 minute (for 'mutable'
resources like `https://gitlab.com/gitlab-org/gitlab-ce/raw/master/VERSION`
which use a branch name) to 1 hour (for immutable resources like
`https://gitlab.com/gitlab-org/gitlab-ce/raw/17de30f412b5eddaa080006b6dd2
aae2bd2d5647/VERSION` that use a commit SHA). In addition to this we
configured NGINX in the Omnibus packages to use up to 1 GB of disk space for
proxy caching. These two changes combined reduce the load on GitLab servers
that get many requests of HTTP clients polling a single file in a public repo.
- In GitLab 8.4 we added a 'housekeeping button' to the project settings page.
This button triggers a [git gc](https://www.kernel.org/pub/software/scm/git/docs/git-gc.html) run on the
project. In GitLab 8.6 we have automated this button: every 10 pushes, but no
more than once per hour, GitLab will run `git gc` on repositories. This should
(slightly) improve Git disk use and performance.
## New GitLab CI Features
@@ -92,6 +139,8 @@ and earlier deployments should [upgrade to this version](http://doc.gitlab.com/o
- New drop downs with multi selection
- New branch from an issue
- SAML customization http://doc.gitlab.com/ee/integration/saml.html#customization
- Easily (un)mark merge request as WIP using link: gitlab-org/gitlab-ce!3006
### Updates in the omnibus-gitlab package
Loading