Release 8.6.0
Merge request reports
Activity
Be sure to mention the "Delete By Query Plugin": https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/205#note_3953508Mention 'You must enable the pg_trgm extension as a PostgreSQL super user': https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2987#note_4114636Edited by Job van der VoortFeatures:
Test coverage display: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2699e
hotkey to edit issuable: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2945ToC in Wikis: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2952Display formatted YAML Frontmatter in Markdown docs: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3072 (Job: Let's not use the screenshot from this MR, it has a broken image in it that makes me ).
Edited by Job van der VoortWe'll need to add some information about the change to the initial login procedure (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3068#note_4117550). Docs were added in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3120.Edited by Job van der VoortAwesome CI features in this release https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3182Edited by Job van der Voortedit by Job: Everything has been added. Thanks @yorickpeterse
Performance Changes
- Search performance has been greatly improved for users using PostgreSQL without using ElasticSearch. This requires the
pg_trgm
extension (see barometer). Merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2987 - Performance of listing commits has been improved: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3123
- Counting of tags and branches on the commits/branches/tags pages is now a bit faster and is cached: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3128
- Performance of retrieving CI services of a project has been improved: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3158
- Large diffs are hidden in merge requests (still WIP, will be in 8.6): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3185
Upgrade Barometer
Starting with GitLab 8.6 PostgreSQL users are required to enable the "pg_trgm" extension. On certain Linux distributions this will require the installation of an extra package. Ubuntu, Fedora, and Debian all ship this extension in the "postgresql-contrib" package. Once installed the extension must be enabled, this must be done before upgrading to GitLab to ensure that all database migrations succeed. This extension can be enabled by running the following as a PostgreSQL super user for every GitLab database:
CREATE EXTENSION IF NOT EXISTS pg_trgm;
To check if the extension is enabled you can run the following query:
SELECT true AS enabled FROM pg_available_extensions WHERE name = 'pg_trgm' AND installed_version IS NOT NULL;
If the extension is enabled this will produce the following output:
enabled --------- t (1 row)
The database migrations that require this extension create a number of indexes concurrently, this means no downtime is required. Enabling extensions also has no impact on uptime.
MySQL users do not need to take any extra steps.
Edited by Job van der Voort- Search performance has been greatly improved for users using PostgreSQL without using ElasticSearch. This requires the
We should write a word about removed
download_url
from Builds API.Edited by Kamil Trzcińskiedit by Job: added, thanks @marin
Other changes
Updates in the omnibus-gitlab package
As GitLab gets improved every release, so does the omnibus-gitlab package. You can see the changes that package receives for every release in the omnibus-gitlab CHANGELOG.
In this release there are some important changes in the bundled software:
- Redis is updated to version 2.8.24
- PostgreSQL is updated to version 9.2.15
- Nginx proxy caching is enabled
- pg_trgm extension is automatically enabled
- Default Nginx http2 support can be disabled if necessary
Edited by Job van der Voort- Edited by Job van der Voort
@stanhu bah typo, thanks!
Merge request https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/260 adds a new setting "verify_ssl" to gitlab.yml which users will have to add to their configuration file as well. See https://gitlab.com/gitlab-org/gitlab-ce/issues/14343 for more information.Edited by Job van der Voort15 Thanks ***MVP_USER_FIRST_NAME***! 16 17 <!--more--> 18 19 ## feature 1 20 21 > [Documentation link](link) 22 23 ## feature 2 24 25 > [Documentation link](link) 26 27 ## Other changes 28 29 This release has more improvements, including security fixes. Please check out [the Changelog](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) to see the all named changes. 30 Proposed update for GitLab Mattermost:
GitLab Mattermost 2.1
Mattermost 2.1 ships in GitLab 8.6 with new Android, Windows, Linux and Mac apps with full GitLab SSO support, plus Brazilian Portuguese translation and more. Mattermost 2.1 contains a security update and earlier deployments should upgrade to this version.
Here's the raw version:
## GitLab Mattermost 2.1 [Mattermost 2.1](http://www.mattermost.org/mattermost-2-1-android-windows-linux-and-mac-apps-plus-portuguese/) ships in GitLab 8.6 with new Android, Windows, Linux and Mac apps with full GitLab SSO support, plus Brazilian Portuguese translation and more. Mattermost 2.1 contains a [security update](http://docs.mattermost.com/administration/changelog.html#security-update) and earlier deployments should [upgrade to this version](http://doc.gitlab.com/omnibus/gitlab-mattermost/).
I added the PostgreSQL changes to the upgrade barometer (including some steps to follow in case poop hits the fan) in commit b08a2f736ad2c4ddbe2e16d6e932c67d1d41f4ab, feel free to adjust/move around if needed.cc @sytses
Edited by Job van der VoortAdded 1 commit:
- 3758cf4d - Added PostgreSQL changes to the upgrade barometer
Job: added. Thanks @yorickpeterse
More performance changes that were added after I wrote my previous comment:
- Project avatars stored in Git repositories are now cached, cutting down request timings for all project pages for projects that don't use an avatar uploaded via the web UI. Merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3272
- Diffs that are larger than 100 KB are no longer displayed, instead a "This diff is too large" message is displayed. This prevents Unicorn timeouts when viewing large diffs. Merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3185
- 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) andgit_hooks.project_id
(https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/271)
Edited by Job van der VoortJob: added. thanks @jschatz1
- Build updates via the Web notifications. https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2604
- A whole new fancy sidebar with multi select labels. https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3175
- Issues and Merge Requests look good on mobile.
- New drop downs with multi selection
Edited by Job van der VoortExternal users, these can only access internal and private projects where they've been explicitly granted access to: gitlab-org/gitlab-ce!3171.Edited by Job van der VoortNew branch from an issue: gitlab-org/gitlab-ce!2808Edited by Job van der VoortConfidential issues: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3282Edited by Job van der VoortAdded 1 commit:
- 03e0256b - Added note about Omnibus users and pg_trgm
Reassigned to @JobV
Added 444 commits:
-
03e0256b...7c4c78bf - 440 commits from branch
master
- c07a040f - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-8-6
- 2fc9e0b1 - es requirements
- 6e87152e - postgres thing
- 466fb408 - fix conflicts
Toggle commit list-
03e0256b...7c4c78bf - 440 commits from branch
Added 1 commit:
- d61893d6 - main list of features
Another performance note: performance of viewing individual issues will be improved by caching certain Git operations, see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3296 for more information.Edited by Job van der VoortWe also upgradedomniauth-saml
to the latest version to add new features: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3170I'm not sure if it's release post worthy, though.Edited by Achilleas PipinellisAdded 1 commit:
- dc6ae335 - SO MANY FEATURES
This is mostly a note for ourselves as the barometer already mentions downtime, but confidential issues (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/227) will require downtime (in case it hasn't already been deployed) as it adds a column to the "issues" table with a default value.
@JobV Easily (un)mark merge request as WIP using link: gitlab-org/gitlab-ce!3006Edited by Job van der Voortthanks @jacobvosmaer, appreciate that I can just c/p this!
- 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 likehttps://gitlab.com/gitlab-org/gitlab-ce/raw/17de30f412b5eddaa080006b6dd2aae2bd2d5647/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 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.
Edited by Job van der Voort- 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
We removeddownload_url
from Builds API. We decided to do that, because it referred to controller action, which requires normal user login. This seems redundant, because we provide an API for downloading artifacts for specific build: http://doc.gitlab.com/ce/api/builds.html#get-build-artifacts.Edited by Job van der Voort@JobV Issue move to another project https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2831, will get merged today probably.Edited by Job van der VoortWe need to let the people know that we faced the problem of the tcp connection being dropped while running the migration to generate the trigram indexes.Edited by Achilleas PipinellisAdded 1 commit:
- 51ae8835 - Add the MVP
Added 1 commit:
- 61f267e6 - add some text
Added 1 commit:
- 429c4d38 - more descriptions
Add a note about the new LDAPGroupSync worker. We split LDAPSyncworker and LDAPGroupSync worker. Performance will be greatly improved for large installations. If you want to provide details: It runs once per hour. In our benchmark runs, for 20,000 users and 10,000 groups, the sync takes 15 minutes. This is in contrast to hours or, in extreme cases, 1-2 days for the old LDAPSyncWorker (which synced groups, too).Edited by Job van der VoortAdded 1 commit:
- cb01d097 - lots more text
Added 1 commit:
- 7587ce0d - highlight performance improvements
Added 1 commit:
- ed9f9206 - ldap performance improvements
@JobV Wanted GIFs for:
- new dropdowns, especially the issues list one where you can make a new label and all
- labels select in sidebar
- anything else you can think of
- Todos with JS
- move issue to another project
-
Here's creating a label. I'm unsure about using it because the button gets cut off (already opened an issue to fix):
-
As far as I can tell, label multi-select did not make it into 8.6 -- @jschatz1?
-
¯\_(ツ)_/¯
-
Hard to show this well in a GIF I think. I'll try.
Edited by Robert SpeicherJob: added
- OAuth authentication
- Wiki synchronization
- SSH keys synchronization
We should recommend any one trying Geo to use 8.6
Edited by Job van der VoortGroup visibility level: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3323 Like with projects, the visibility of a group can be set to dictate whether anonymous users, all signed in users, or only explicit group members can view it. The restriction for visibility levels on the application setting level also applies to groups, so if that's set tointernal
, the explore page will be empty for anonymous users. The group page now has a visibility level icon. Solves this popular issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/12658Edited by Job van der VoortThanks @rspeicher @brodock @DouweM
Added 1 commit:
- 7d6a5d5e - updates to post