Skip to content
Snippets Groups Projects
Commit 31da1fe9 authored by Marcia Ramos's avatar Marcia Ramos
Browse files

add content

parent 63e3a8fe
No related branches found
No related tags found
3 merge requests!6084Add markdown support to YAML entries,!5937Automate release posts custom styling,!5551GitLab 9.2 release post
Pipeline #
Loading
Loading
@@ -131,6 +131,16 @@ features:
 
<p>We've also styled labels there too with the right colors.
 
- name: Terraform Support for GitLab Runner
available_in: [ce, ees, eep]
documentation_link: ''
image_url: ''
description: |
As part of GitLab 9.1, we launched support for installing GitLab on GCE via
<a href="https://www.hashicorp.com/">Hashicorp's</a> <a href="https://www.terraform.io/">Terraform</a>.
With 9.2 we are also adding the ability to deploy GitLab Runner as well,
allowing you to complete the idea to production cycle!
- name: Primary Feature 3
available_in: [ce, ees, eep]
documentation_link: ''
Loading
Loading
@@ -305,6 +315,79 @@ features:
cache, so even in edge cases you can always rely on your artifacts to be
the latest version.
 
- name: Handling of Pmbiguous Poutes in Pynamic Paths
available_in: [ce, ees, eep]
documentation_link: 'https://docs.gitlab.com/ce/user/group/subgroups/index.html#creating-a-subgroup'
documentation_text: "More info on creating subgroups is available in the documentation."
description: |
<p>There are several paths that GitLab uses to access certain features. With the introduction of nested groups these features could become unavailable for projects or groups with names that conflict with these paths. For example: for a project called 'badges' the build and coverage status badges would become unavailable.
<p>To avoid confusion, it is now no longer possible to create projects or groups with names that could clash with existing GitLab routes.
<p>If you had any projects or groups named like one of these routes, they will have been automatically renamed during the upgrade. A project named <code>badges</code> would be renamed to <code>badges0</code>.</p>
<p>Keep in mind that git-remotes would need to be updated locally as well. That can be done like this:</p>
<pre><code>git remote set-url origin &lt;git@gitlab.com:the-updated-path/the-updated-name.git&gt;
</code></pre>
<p>The full list of reserved words can be found in the <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/validators/dynamic_path_validator.rb"><code>dynamic_path_validator.rb</code> file</a>. The list of existing projects and groups that were renamed in this release can be found in the <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/master/db/post_migrate/20170412174900_rename_reserved_dynamic_paths.rb">migration</a> that renamed them.</p>
- name: Deploys Displayed on Environment Performance Dashboard
available_in: [ce, ees, eep]
documentation_link:
image_url: '/images/9_2/environment_deploy_tag.png'
description: |
When investigating a change in performance behavior, one of the first questions
asked is always if there have been any changes to the environment. GitLab 9.2
now quickly answers this question by showing all deployments to an environment
directly on the monitoring dashboard. This allows easy correlation between any
changes in performance and a new version of the app, all without leaving GitLab!
- name: GitLab Runner 9.2
available_in: [ce, ees, eep] # MISSING
documentation_link: 'https://docs.gitlab.com/runner/'
documentation_text: "Learn more about GitLab Runner in our docs."
image_url:
description: |
<p>We're also releasing GitLab Runner 9.2 today!
<p><strong>Most interesting changes:</strong>
<ul>
<li>Support for TLS client authentication (<a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/157">merge request</a>)</li>
<li>PosLabels setting for Kubernetes executor configuration (<a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/558">merge request</a>)</li>
<li>Support for Kubernetes Service Account in Kubernetes executor configuration (<a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/554">merge request</a>)</li>
</ul>
<p>List of all changes can be found in GitLab Runner's <a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/v9.2.0/CHANGELOG.md">CHANGELOG</a>.</p>
- name: Omnibus Improvements
available_in: [ce, ees, eep]
documentation_link:
image_url:
description: |
<h4 id="gitlab-mattermost-3_9">GitLab Mattermost 3.9</h4>
<p>GitLab 9.2 includes <a href="https://about.mattermost.com/mattermost-3-9">Mattermost 3.9</a>, <a href="https://about.mattermost.com/">an open source Slack-alternative</a>, which adds a new <a href="https://about.mattermost.com/community-applications/#privateApps">integrations directory</a>, Polish support, upgraded desktop apps with spellchecker, and much more.</p>
<p>This version includes <a href="http://about.mattermost.com/security-updates/">security updates</a> and an upgrade is recommended.</p>
<h4 id="gitlabregistry">GitLab Registry</h4>
<p>The GitLab Container Registry has been updated from 2.4 to 2.6.1.</p>
- name: Usage Ping
available_in: [ce, ees, eep]
documentation_link:
image_url:
description: |
<p>This release contains two changes to the usage ping: you can <a href="https://docs.gitlab.com/ce/user/admin_area/settings/usage_statistics.html#deactivate-the-usage-ping">now opt-out</a> of the usage ping through your configuration in <code>gitlab.rb</code>. This allows you to turn off the usage ping before having started GitLab. You were already able to opt-out through the administration panel and this remains the case.
In addition, we now include the hostname in the usage ping, similar to the <a href="https://docs.gitlab.com/ce/user/admin_area/settings/usage_statistics.html#version-check">version check</a>. For more, see <a href="https://docs.gitlab.com/ce/user/admin_area/settings/usage_statistics.html#usage-ping">the documentation on the usage ping</a>.</p>
- name: Performance Improvements
available_in: [ce, ees, eep]
documentation_link:
image_url:
description: |
<p>With every release of GitLab we look to make significant improvements to the performance. In GitLab 9.2, the following areas should see visible improvement:</p>
<ul>
<li>Listing groups</li>
<li>Listing projects</li>
<li>Listing merge requests</li>
<li>Listing milestones</li>
<li>Push mirrors should no longer put pressure on filesystem and sidekiq queues</li>
</ul>
<p><a href="https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&amp;utf8=%E2%9C%93&amp;state=opened&amp;label_name[]=performance&amp;milestone_title=9.2">Here is a full list</a> of performance improvements in GitLab 9.2.</p>
# MVP
mvp:
fullname: Dosuken Shinya
Loading
Loading
@@ -330,15 +413,31 @@ cta:
# UPGRADE BAROMETER
barometer:
description: |
description (supports HTML) Lorem ipsum dolor sit amet, consectetur adipisicing elit. Doloremque repellendus tempora voluptatibus est. Dignissimos nostrum, tenetur explicabo, iste aliquid sint expedita! Voluptas fugit natus voluptates ad recusandae maxime repellat blanditiis?
<p>To upgrade to GitLab 9.2, no downtime is required.</p>
<p>However to enable <a href="#auto-cancel-redundant-pipelines-now-set-to-on-for-all-projects">automatic cancellation of redundant pipelines</a> for all projects, the post deployment migration might take significant time depending on your installation size.</p>
<p>Starting with GitLab 9.1.0 it's possible to upgrade to a newer version of GitLab
without having to take your GitLab instance offline. However, for this to work
there are the following requirements:</p>
<ol>
<li>You can only upgrade 1 release at a time. For example, if 9.1.15 is the last
release of 9.1 then you can safely upgrade from that version to 9.2.0.
However, if you are running 9.1.14 you first need to upgrade to 9.1.15.</li>
<li>You have to use <a href="https://docs.gitlab.com/ce/development/post_deployment_migrations.html">post-deployment migrations</a>.</li>
<li>You are using PostgreSQL. If you are using MySQL you will still need downtime
when upgrading.</li>
</ol>
<p>This applies to major, minor, and patch releases unless stated otherwise in a
release post.</p>
<p>A new version of our API was released in <a href="https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#api-v4">GitLab 9.0</a>.
While existing calls to API v3 will continue to work until August 2017, we
advise you to make any necessary changes to applications that use the v3 API.
<a href="https://docs.gitlab.com/ee/api/v3_to_v4.html">Read the documentation</a> to learn
more.</p>
 
# DEPRECATIONS
deprecations:
- feature_name: XXX Deprecated
due: April 2017
description: |
description (supports HTML) Lorem ipsum dolor sit amet, consectetur adipisicing elit. Voluptatibus totam, esse eius quibusdam atque tenetur.
- feature_name: YYY Deprecated
due: # due date
- feature_name: Vendor support for Ubuntu 12.04 and OpenSUSE 13.2
due: May 22nd, 2017.
description: |
description (supports HTML) Lorem ipsum dolor sit amet, consectetur adipisicing elit. Eveniet corporis fugiat nobis suscipit tempora obcaecati, magni nemo quod neque quae.
Vendor support for Ubuntu 12.04 and OpenSUSE 13.2 has ended.
GitLab will no longer provide support or packages for these platforms.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment