New upstream version 13.1.6
This commit is contained in:
parent
b8c1f2cd92
commit
f7a89b7334
17 changed files with 32 additions and 23 deletions
|
@ -2,6 +2,14 @@
|
|||
documentation](doc/development/changelog.md) for instructions on adding your own
|
||||
entry.
|
||||
|
||||
## 13.1.6 (2020-08-05)
|
||||
|
||||
- No changes.
|
||||
|
||||
## 13.1.5 (2020-07-23)
|
||||
|
||||
- No changes.
|
||||
|
||||
## 13.1.4 (2020-07-09)
|
||||
|
||||
### Fixed (4 changes)
|
||||
|
|
|
@ -1 +1 @@
|
|||
13.1.4
|
||||
13.1.6
|
||||
|
|
2
VERSION
2
VERSION
|
@ -1 +1 @@
|
|||
13.1.4
|
||||
13.1.6
|
||||
|
|
|
@ -70,14 +70,14 @@ module WorkerAttributes
|
|||
|
||||
# Set this attribute on a job when it will call to services outside of the
|
||||
# application, such as 3rd party applications, other k8s clusters etc See
|
||||
# doc/development/sidekiq_style_guide.md#Jobs-with-External-Dependencies for
|
||||
# doc/development/sidekiq_style_guide.md#jobs-with-external-dependencies for
|
||||
# details
|
||||
def worker_has_external_dependencies!
|
||||
worker_attributes[:external_dependencies] = true
|
||||
end
|
||||
|
||||
# Returns a truthy value if the worker has external dependencies.
|
||||
# See doc/development/sidekiq_style_guide.md#Jobs-with-External-Dependencies
|
||||
# See doc/development/sidekiq_style_guide.md#jobs-with-external-dependencies
|
||||
# for details
|
||||
def worker_has_external_dependencies?
|
||||
worker_attributes[:external_dependencies]
|
||||
|
|
|
@ -48,7 +48,7 @@ Example response:
|
|||
"sign_in_text" : null,
|
||||
"container_expiration_policies_enable_historic_entries": true,
|
||||
"container_registry_token_expire_delay": 5,
|
||||
"repository_storages": ["default"],
|
||||
"repository_storages_weighted": {"default": 100},
|
||||
"plantuml_enabled": false,
|
||||
"plantuml_url": null,
|
||||
"terminal_max_session_time": 0,
|
||||
|
@ -314,7 +314,8 @@ are listed in the descriptions of the relevant settings.
|
|||
| `receive_max_input_size` | integer | no | Maximum push size (MB). |
|
||||
| `repository_checks_enabled` | boolean | no | GitLab will periodically run `git fsck` in all project and wiki repositories to look for silent disk corruption issues. |
|
||||
| `repository_size_limit` | integer | no | **(PREMIUM)** Size limit per repository (MB) |
|
||||
| `repository_storages` | array of strings | no | A list of names of enabled storage paths, taken from `gitlab.yml`. New projects will be created in one of these stores, chosen at random. |
|
||||
| `repository_storages` | array of strings | no | (GitLab 13.0 and earlier) List of names of enabled storage paths, taken from `gitlab.yml`. New projects are created in one of these stores, chosen at random. |
|
||||
| `repository_storages_weighted` | hash of strings to integers | no | (GitLab 13.1 and later) Hash of names of taken from `gitlab.yml` to weights. New projects are created in one of these stores, chosen by a weighted random selection. |
|
||||
| `require_two_factor_authentication` | boolean | no | (**If enabled, requires:** `two_factor_grace_period`) Require all users to set up Two-factor authentication. |
|
||||
| `restricted_visibility_levels` | array of strings | no | Selected levels cannot be used by non-admin users for groups, projects or snippets. Can take `private`, `internal` and `public` as a parameter. Default is `null` which means there is no restriction. |
|
||||
| `rsa_key_restriction` | integer | no | The minimum allowed bit length of an uploaded RSA key. Default is `0` (no restriction). `-1` disables RSA keys. |
|
||||
|
|
|
@ -567,7 +567,7 @@ For monitoring deployed apps, see the [Sentry integration docs](../user/project/
|
|||
- [GDK](https://gitlab.com/gitlab-org/gitlab/blob/master/config/gitlab.yml.example)
|
||||
- Layer: Core Service (Processor)
|
||||
- Process: `sidekiq`
|
||||
- GitLab.com: [Sidekiq](../user/gitlab_com/index.md#Sidekiq)
|
||||
- GitLab.com: [Sidekiq](../user/gitlab_com/index.md#sidekiq)
|
||||
|
||||
Sidekiq is a Ruby background job processor that pulls jobs from the Redis queue and processes them. Background jobs allow GitLab to provide a faster request/response cycle by moving work into the background.
|
||||
|
||||
|
|
|
@ -646,7 +646,7 @@ defaultClient.query({ query })
|
|||
.then(result => console.log(result));
|
||||
```
|
||||
|
||||
When [using Vuex](#Using-with-Vuex), disable the cache when:
|
||||
When [using Vuex](#using-with-vuex), disable the cache when:
|
||||
|
||||
- The data is being cached elsewhere
|
||||
- The use case does not need caching
|
||||
|
|
|
@ -115,6 +115,6 @@ There are multiple ways to find the source of queries.
|
|||
|
||||
## See also
|
||||
|
||||
- [Bullet](profiling.md#Bullet) For finding `N+1` query problems
|
||||
- [Bullet](profiling.md#bullet) For finding `N+1` query problems
|
||||
- [Performance guidelines](performance.md)
|
||||
- [Merge request performance guidelines](merge_request_performance_guidelines.md#query-counts)
|
||||
|
|
|
@ -741,7 +741,7 @@ GitLab uses [factory_bot](https://github.com/thoughtbot/factory_bot) as a test f
|
|||
- There should be only one top-level factory definition per file.
|
||||
- FactoryBot methods are mixed in to all RSpec groups. This means you can (and
|
||||
should) call `create(...)` instead of `FactoryBot.create(...)`.
|
||||
- Make use of [traits](https://www.rubydoc.info/gems/factory_bot/file/GETTING_STARTED.md#Traits) to clean up definitions and usages.
|
||||
- Make use of [traits](https://www.rubydoc.info/gems/factory_bot/file/GETTING_STARTED.md#traits) to clean up definitions and usages.
|
||||
- When defining a factory, don't define attributes that are not required for the
|
||||
resulting record to pass validation.
|
||||
- When instantiating from a factory, don't supply attributes that aren't
|
||||
|
|
|
@ -638,7 +638,7 @@ That concludes the configuration changes for our GitLab instance. Next, we'll cr
|
|||
|
||||
On the EC2 dashboard:
|
||||
|
||||
1. Select the `GitLab` instance we [created earlier](#install-gitLab).
|
||||
1. Select the `GitLab` instance we [created earlier](#install-gitlab).
|
||||
1. Click on **Actions**, scroll down to **Image** and click **Create Image**.
|
||||
1. Give your image a name and description (we'll use `GitLab-Source` for both).
|
||||
1. Leave everything else as default and click **Create Image**
|
||||
|
|
|
@ -11,7 +11,7 @@ These instructions will also work for a self-managed GitLab instance. However, y
|
|||
need to ensure your own [Runners are configured](../../ci/runners/README.md) and
|
||||
[Google OAuth is enabled](../../integration/google.md).
|
||||
|
||||
**Note**: GitLab's Web Application Firewall is deployed with [Ingress](../../user/clusters/applications.md#Ingress),
|
||||
**Note**: GitLab's Web Application Firewall is deployed with [Ingress](../../user/clusters/applications.md#ingress),
|
||||
so it will be available to your applications no matter how you deploy them to Kubernetes.
|
||||
|
||||
## Configuring your Google account
|
||||
|
|
|
@ -222,7 +222,7 @@ a `before_script` execution to prepare your scan job.
|
|||
|
||||
To pass your project's dependencies as artifacts, the dependencies must be included
|
||||
in the project's working directory and specified using the `artifacts:path` configuration.
|
||||
If all dependencies are present, the `-compile=false` flag can be provided to the
|
||||
If all dependencies are present, the `COMPILE=false` variable can be provided to the
|
||||
analyzer and compilation will be skipped:
|
||||
|
||||
```yaml
|
||||
|
@ -247,10 +247,9 @@ build:
|
|||
spotbugs-sast:
|
||||
dependencies:
|
||||
- build
|
||||
script:
|
||||
- /analyzer run -compile=false
|
||||
variables:
|
||||
MAVEN_REPO_PATH: ./.m2/repository
|
||||
COMPILE: false
|
||||
artifacts:
|
||||
reports:
|
||||
sast: gl-sast-report.json
|
||||
|
@ -315,11 +314,12 @@ The following variables configure the Docker-in-Docker orchestrator, and therefo
|
|||
|
||||
Some analyzers can be customized with environment variables.
|
||||
|
||||
| Environment variable | Analyzer | Description |
|
||||
|-----------------------------|----------|-------------|
|
||||
| Environment variable | Analyzer | Description |
|
||||
|---------------------------------------|----------------------|-------------|
|
||||
| `SCAN_KUBERNETES_MANIFESTS` | Kubesec | Set to `"true"` to scan Kubernetes manifests. |
|
||||
| `KUBESEC_HELM_CHARTS_PATH` | Kubesec | Optional path to Helm charts that `helm` will use to generate a Kubernetes manifest that `kubesec` will scan. If dependencies are defined, `helm dependency build` should be ran in a `before_script` to fetch the necessary dependencies. |
|
||||
| `KUBESEC_HELM_OPTIONS` | Kubesec | Additional arguments for the `helm` executable. |
|
||||
| `COMPILE` | SpotBugs | Set to `false` to disable project compilation and dependency fetching. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/195252) in GitLab 13.1. |
|
||||
| `ANT_HOME` | SpotBugs | The `ANT_HOME` environment variable. |
|
||||
| `ANT_PATH` | SpotBugs | Path to the `ant` executable. |
|
||||
| `GRADLE_PATH` | SpotBugs | Path to the `gradle` executable. |
|
||||
|
|
|
@ -148,7 +148,7 @@ requests you're assigned to.
|
|||
|
||||
[Snippets](snippets.md) are code blocks that you want to store in GitLab, from which
|
||||
you have quick access to. You can also gather feedback on them through
|
||||
[Discussions](#Discussions).
|
||||
[Discussions](#discussions).
|
||||
|
||||
## Keyboard shortcuts
|
||||
|
||||
|
|
|
@ -92,7 +92,7 @@ to change.
|
|||
GitLab makes full use of the standard (CommonMark) formatting, but also includes additional
|
||||
functionality useful for GitLab users.
|
||||
|
||||
It makes use of [new Markdown features](#new-GFM-markdown-extensions),
|
||||
It makes use of [new Markdown features](#new-gfm-markdown-extensions),
|
||||
not found in standard Markdown:
|
||||
|
||||
- [Color "chips" written in HEX, RGB or HSL](#colors)
|
||||
|
|
|
@ -88,7 +88,7 @@ An issue can be assigned to:
|
|||
|
||||
- Yourself.
|
||||
- Another person.
|
||||
- [Many people](#multiple-assignees-STARTER). **(STARTER)**
|
||||
- [Many people](#multiple-assignees-starter). **(STARTER)**
|
||||
|
||||
The assignee(s) can be changed as often as needed. The idea is that the assignees are
|
||||
responsible for that issue until it's reassigned to someone else to take it from there.
|
||||
|
|
|
@ -52,7 +52,7 @@ RUN rm -f chromedriver_linux64.zip
|
|||
# Install K3d local cluster support
|
||||
# https://github.com/rancher/k3d
|
||||
#
|
||||
RUN curl -s https://raw.githubusercontent.com/rancher/k3d/master/install.sh | TAG="v${K3D_VERSION}" bash
|
||||
RUN curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | TAG="v${K3D_VERSION}" bash
|
||||
|
||||
##
|
||||
# Install gcloud and kubectl CLI used in Auto DevOps test to create K8s
|
||||
|
|
|
@ -53,7 +53,7 @@ describe 'Every Sidekiq worker' do
|
|||
|
||||
# All Sidekiq worker classes should declare a valid `feature_category`
|
||||
# or explicitly be excluded with the `feature_category_not_owned!` annotation.
|
||||
# Please see doc/development/sidekiq_style_guide.md#Feature-Categorization for more details.
|
||||
# Please see doc/development/sidekiq_style_guide.md#feature-categorization for more details.
|
||||
it 'has a feature_category or feature_category_not_owned! attribute', :aggregate_failures do
|
||||
workers_without_defaults.each do |worker|
|
||||
expect(worker.get_feature_category).to be_a(Symbol), "expected #{worker.inspect} to declare a feature_category or feature_category_not_owned!"
|
||||
|
@ -62,7 +62,7 @@ describe 'Every Sidekiq worker' do
|
|||
|
||||
# All Sidekiq worker classes should declare a valid `feature_category`.
|
||||
# The category should match a value in `config/feature_categories.yml`.
|
||||
# Please see doc/development/sidekiq_style_guide.md#Feature-Categorization for more details.
|
||||
# Please see doc/development/sidekiq_style_guide.md#feature-categorization for more details.
|
||||
it 'has a feature_category that maps to a value in feature_categories.yml', :aggregate_failures do
|
||||
workers_with_feature_categories = workers_without_defaults
|
||||
.select(&:get_feature_category)
|
||||
|
|
Loading…
Reference in a new issue