Skip to content
Snippets Groups Projects

Release post - GitLab 11.4

Merged James Ramsay (ex-GitLab) requested to merge release-11-4 into master
Compare and Show latest version
10 files
+ 235
7
Compare changes
  • Side-by-side
  • Inline
Files
10
@@ -144,6 +144,82 @@ features:
Git protocol v2 is supported from Git v2.18.0 and is opt-in. To enable
globally run `git config --global protocol.version=2`.
- name: "Move ability to use includes in .gitlab-ci.yml from starter to core"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#include' # required
reporter: jlenny # required
team: verify # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/42861' # required
description: | # supports markdown
We are very happy to announce in this release that the usage of
includes within the gitlab-ci.yml has become a free feature. This
will help ensure templates and other shared resources are always
compatible between free and non-free users, and also unlocks the
ability for everyone to do best-practice development using reusable
snippets in your CI/CD pipelines.
- name: "Run jobs only/except when there are modifications on a given path or file"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#changes' # required
reporter: jlenny # required
team: verify # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/19232' # required
description: | # supports markdown
A very popularly requested feature, we're very proud now to be offering the
ability within the .gitlab-ci.yml to use only/except rules for jobs
based on when modifications occur to a specific file or path (glob).
This will allow more control for users whose repos contain different
kinds of assets or builds, ensuring only the appropriate steps are
executed for the kinds of changes that were committed.
- name: "Add feature flags for applications (ALPHA)"
available_in: [premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/user/project/operations/feature-flags' # required
image_url: '/images/11_4/feature-flags.png' # required
reporter: jlenny # required
team: release # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6220' # required
description: | # supports markdown
This feature gives you the ability to configure and manage feature flags for
your software directly in the product. Simply create a new feature
flag, validate it using the simple API instructions in your software,
and you have the ability to control the behavior of your software
in the field via the feature flag within GitLab itself.
Note that this is an alpha feature being introduced for the first time,
so while we encourage you to check out the feature and provide feedback
we want you to be aware that the implementation could change in subsequent
releases.
- name: "Add timed incremental rollouts to AutoDevOps"
available_in: [premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/topics/autodevops/#timed-incremental-rollout-to-production' # required
image_url: '/images/11_4/timed-incremental-rollouts.png' # required
reporter: jlenny # required
team: release # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/7545' # required
description: | # supports markdown
You've had the ability within AutoDevOps to setup incremental
rollouts for a while now, and with this release we are adding
an option to also set up _timed_ incremental rollouts where
the rollout will automatically continue on a timed cadence
unless there is some error.
- name: "Make GitLab Pages support access control"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/user/project/pages/#getting-started' # required
image_url: '/images/11_4/pages-access-control.png' # required
reporter: jlenny # required
team: release # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/33422' # required
description: | # supports markdown
You've had the ability within AutoDevOps to setup incremental
rollouts for a while now, and with this release we are adding
an option to also set up _timed_ incremental rollouts where
the rollout will automatically continue on a timed cadence
unless there is some error.
- name: "Lorem ipsum"
available_in: [core, starter, premium, ultimate] # required
gitlab_com: false # required if the feature is NOT available in GitLab.com. Else, delete this line.
@@ -159,6 +235,62 @@ features:
# SECONDARY FEATURES
secondary:
- name: "Click to insert Markdown table"
available_in: [core, starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/markdown.html'
image_url: '/images/11_4/table-markdown.png'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/29788'
description: |
GitLab supports GitLab-flavored Markdown (GFM) in most places throughout
GitLab where you enter text, providing the power of rich formatting with
a simple syntax. In particular, you can create tables in GFM. Previously,
this was painful to use, especially for large tables, since you had to type
a lot of characters or paste in a previous table just to format it the way
you want.
With this release, you can now click on the table button in the GFM editor,
and this will automatically insert a table for you. You can then easily
enter table values or extend the table, formatting it just the way you want.
You can use this in description and comment boxes all throughout GitLab.
Thank you [George Tsiolis](https://gitlab.com/gtsiolis) for the contribution!
- name: "Highlight @mentions for yourself distinctly"
available_in: [core, starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/issues/issues_functionalities.html#13-mentions'
image_url: '/images/11_4/highlight-yourself-distinct.png'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/49036'
description: |
When collaborating in a long discussion in an issue or merge request, often
many users are involved, making it difficult to quickly at a glance, see
comments that are directed at you.
With this release, @mentions for yourself (i.e. the current user), are highlighted
in a different color, allowing you to easily see which comments involve you,
helping you focus on them quickly.
- name: "Include new issues created in burndown chart"
available_in: [starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/milestones/burndown_charts.html'
image_url: '/images/11_4/burndown-chart.png'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6174'
description: |
Burndown charts help teams track work, as it progresses throughout a milestone.
Usually, the scope of work is decided and agreed on before the milestone
begins. But occasionally, there will be important exceptions to the rule,
(such as an emergency bug or security fix) and new scope needs to be included,
in the form of new issues.
With this release, the burndown chart now accounts for these
new issues that are created in the middle of a milestone, resulting in an
uptick of the line in a burndown chart.
- name: "Expanded weight values in issues API"
available_in: [starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/api/issues.html'
@@ -304,6 +436,45 @@ features:
Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)
- name: "Filter Admin Runners view by Runner Type and State"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/ci/runners/' # required
image_url: '/images/11_4/runner-admin-filter.png' # required
reporter: jlenny # required
team: release # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/36781' # required
description: | # supports markdown
The admin runner view now supports the ability to filter
by runner type and state, giving you more options to manage
especially large fleets of runners in your environment.
- name: "Add support for interactive web terminal to Docker executor"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/ci/interactive_web_terminal/' # required
reporter: jlenny # required
team: verify # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-runner/issues/3467' # required
description: | # supports markdown
The interactive web terminals feature has been expanded to be
compatible with Docker executors as well. For now, the Docker session
is closed as soon as the script exits, but we are aiming to further
improve this behavior by resolving [#3605](https://gitlab.com/gitlab-org/gitlab-runner/issues/3605) in
our next release.
- name: "Allow pipelines to schedule delayed job runs"
available_in: [core, starter, premium, ultimate] # required
documentation_link: 'https://docs.gitlab.com/ee/ci/pipelines.html#delay-a-particular-job-in-the-pipeline-graph' # required
reporter: jlenny # required
team: verify # required
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/51352' # required
description: | # supports markdown
It is now possible to set a job to start after a delay timer
via the .gitlab-ci.yml. The timer starts ticking when the job
would have otherwise started, giving you control to implement
tasks that need to wait for a period of time to occur - for
example, when implementing timed incremental rollouts, or any
other delays needed after performing some other action.
- name: "Lorem ipsum"
available_in: [premium, ultimate] # required
gitlab_com: false # required if the feature is NOT available in GitLab.com. Else, delete this line.
Loading