Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
ad7ce32986
commit
3e78ae6ec1
|
|
@ -0,0 +1,9 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
class AddStorageSizeLimitToPlanLimit < ActiveRecord::Migration[6.0]
|
||||
DOWNTIME = false
|
||||
|
||||
def change
|
||||
add_column :plan_limits, :storage_size_limit, :integer, default: 0, null: false
|
||||
end
|
||||
end
|
||||
|
|
@ -5032,7 +5032,8 @@ CREATE TABLE public.plan_limits (
|
|||
ci_project_subscriptions integer DEFAULT 2 NOT NULL,
|
||||
ci_pipeline_schedules integer DEFAULT 10 NOT NULL,
|
||||
offset_pagination_limit integer DEFAULT 50000 NOT NULL,
|
||||
ci_instance_level_variables integer DEFAULT 25 NOT NULL
|
||||
ci_instance_level_variables integer DEFAULT 25 NOT NULL,
|
||||
storage_size_limit integer DEFAULT 0 NOT NULL
|
||||
);
|
||||
|
||||
CREATE SEQUENCE public.plan_limits_id_seq
|
||||
|
|
@ -14163,5 +14164,6 @@ COPY "schema_migrations" (version) FROM STDIN;
|
|||
20200623000148
|
||||
20200623000320
|
||||
20200623121135
|
||||
20200624075411
|
||||
\.
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,6 @@ You can add a command to your `.gitlab-ci.yml` file to
|
|||
|
||||
| Variable | GitLab | Runner | Description |
|
||||
|-----------------------------------------------|--------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `ARTIFACT_DOWNLOAD_ATTEMPTS` | 8.15 | 1.9 | Number of attempts to download artifacts running a job |
|
||||
| `CHAT_CHANNEL` | 10.6 | all | Source chat channel which triggered the [ChatOps](../chatops/README.md) command |
|
||||
| `CHAT_INPUT` | 10.6 | all | Additional arguments passed in the [ChatOps](../chatops/README.md) command |
|
||||
| `CI` | all | 0.4 | Mark that job is executed in CI environment |
|
||||
|
|
@ -130,11 +129,9 @@ You can add a command to your `.gitlab-ci.yml` file to
|
|||
| `CI_SERVER_VERSION_MINOR` | 11.4 | all | GitLab version minor component |
|
||||
| `CI_SERVER_VERSION_PATCH` | 11.4 | all | GitLab version patch component |
|
||||
| `CI_SHARED_ENVIRONMENT` | all | 10.1 | Marks that the job is executed in a shared environment (something that is persisted across CI invocations like `shell` or `ssh` executor). If the environment is shared, it is set to true, otherwise it is not defined at all. |
|
||||
| `GET_SOURCES_ATTEMPTS` | 8.15 | 1.9 | Number of attempts to fetch sources running a job |
|
||||
| `GITLAB_CI` | all | all | Mark that job is executed in GitLab CI/CD environment |
|
||||
| `GITLAB_FEATURES` | 10.6 | all | The comma separated list of licensed features available for your instance and plan |
|
||||
| `GITLAB_USER_EMAIL` | 8.12 | all | The email of the user who started the job |
|
||||
| `GITLAB_USER_ID` | 8.12 | all | The ID of the user who started the job |
|
||||
| `GITLAB_USER_LOGIN` | 10.0 | all | The login username of the user who started the job |
|
||||
| `GITLAB_USER_NAME` | 10.0 | all | The real name of the user who started the job |
|
||||
| `RESTORE_CACHE_ATTEMPTS` | 8.15 | 1.9 | Number of attempts to restore the cache running a job |
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Accessibility
|
||||
# Accessibility & Readability
|
||||
|
||||
## Resources
|
||||
|
||||
|
|
|
|||
|
|
@ -495,15 +495,19 @@ older tags and images are regularly removed from the Container Registry.
|
|||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15398) in GitLab 12.8.
|
||||
|
||||
For a specific project, if you want to remove tags you no longer need,
|
||||
you can create an expiration policy. When the policy is applied, tags matching the regex pattern are removed.
|
||||
The underlying layers and images remain.
|
||||
|
||||
To delete the underlying layers and images no longer associated with any tags, Instance Administrators can use
|
||||
[garbage collection](../../../administration/packages/container_registry.md#removing-unused-layers-not-referenced-by-manifests) with the `-m` switch.
|
||||
|
||||
NOTE: **Note:**
|
||||
For GitLab.com, expiration policies are not available for projects created before GitLab 12.8.
|
||||
For self-managed instances, expiration policies may be enabled by an admin in the
|
||||
[CI/CD Package Registry settings](./../../admin_area/settings/index.md#cicd).
|
||||
Note the inherent [risks involved](./index.md#use-with-external-container-registries).
|
||||
|
||||
It is possible to create a per-project expiration policy, so that you can make sure that
|
||||
older tags and images are regularly removed from the Container Registry.
|
||||
|
||||
The expiration policy algorithm starts by collecting all the tags for a given repository in a list,
|
||||
then goes through a process of excluding tags from it until only the ones to be deleted remain:
|
||||
|
||||
|
|
|
|||
|
|
@ -52,6 +52,7 @@ RSpec.describe PlanLimits do
|
|||
ci_active_pipelines
|
||||
ci_pipeline_size
|
||||
ci_active_jobs
|
||||
storage_size_limit
|
||||
]
|
||||
end
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue