diff --git a/.gitlab/merge_request_templates/Stable Branch.md b/.gitlab/merge_request_templates/Stable Branch.md index 4ad8e6fc8a2..7130067b1f2 100644 --- a/.gitlab/merge_request_templates/Stable Branch.md +++ b/.gitlab/merge_request_templates/Stable Branch.md @@ -18,6 +18,7 @@ This checklist encourages us to confirm any changes have been analyzed to reduce * [ ] This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. * [ ] The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). * [ ] This MR has a [severity label] assigned (if applicable). +* [ ] Set the milestone of the merge request to match the target backport branch version. * [ ] This MR has been approved by a maintainer (only one approval is required). * [ ] Ensure the `e2e:package-and-test-ee` job has either succeeded or been approved by a Software Engineer in Test. diff --git a/app/views/external_redirect/external_redirect/index.html.haml b/app/views/external_redirect/external_redirect/index.html.haml index 36bf98cba02..9ef2b21d84c 100644 --- a/app/views/external_redirect/external_redirect/index.html.haml +++ b/app/views/external_redirect/external_redirect/index.html.haml @@ -1,4 +1,3 @@ -- add_page_specific_style 'page_bundles/external_redirect' - page_title _("You're about to leave GitLab") - url = local_assigns.fetch(:url) diff --git a/doc/administration/settings/continuous_integration.md b/doc/administration/settings/continuous_integration.md index ce41950301e..4cb24a77e79 100644 --- a/doc/administration/settings/continuous_integration.md +++ b/doc/administration/settings/continuous_integration.md @@ -435,11 +435,16 @@ To disable your instance fetching this data: ## Troubleshooting -### 413 Request Entity Too Large +### `413 Request Entity Too Large` error -When build jobs fail with the following error, -increase the [maximum artifacts size](#maximum-artifacts-size). +If the artifacts are too large, the job might fail with the following error: ```plaintext Uploading artifacts as "archive" to coordinator... too large archive responseStatus=413 Request Entity Too Large status=413" at end of a build job on pipeline when trying to store artifacts to . ``` + +You might need to: + +- Increase the [maximum artifacts size](#maximum-artifacts-size). +- If you are using NGINX as a proxy server, increase the file upload size limit which is limited to 1 MB by default. + Set a higher value for `client-max-body-size` in the NGINX configuration file. diff --git a/doc/api/job_artifacts.md b/doc/api/job_artifacts.md index 3f6f6606dbe..a83e32869fe 100644 --- a/doc/api/job_artifacts.md +++ b/doc/api/job_artifacts.md @@ -18,7 +18,7 @@ available in the Premium and Ultimate tier. Get the job's artifacts zipped archive of a project. If you use cURL to download artifacts from GitLab.com, use the `--location` parameter -as the request might redirect through a CND. +as the request might redirect through a CDN. ```plaintext GET /projects/:id/jobs/:job_id/artifacts @@ -80,7 +80,7 @@ is the same as [getting the job's artifacts](#get-job-artifacts), but by defining the job's name instead of its ID. If you use cURL to download artifacts from GitLab.com, use the `--location` parameter -as the request might redirect through a CND. +as the request might redirect through a CDN. NOTE: If a pipeline is [parent of other child pipelines](../ci/pipelines/downstream_pipelines.md#parent-child-pipelines), artifacts @@ -148,7 +148,7 @@ the job's artifacts zipped archive. The file is extracted from the archive and streamed to the client. If you use cURL to download artifacts from GitLab.com, use the `--location` parameter -as the request might redirect through a CND. +as the request might redirect through a CDN. ```plaintext GET /projects/:id/jobs/:job_id/artifacts/*artifact_path @@ -194,7 +194,7 @@ are searched in hierarchical order from parent to child. For example, if both pa have a job with the same name, the artifact from the parent pipeline is returned. If you use cURL to download artifacts from GitLab.com, use the `--location` parameter -as the request might redirect through a CND. +as the request might redirect through a CDN. ```plaintext GET /projects/:id/jobs/artifacts/:ref_name/raw/*artifact_path?job=name diff --git a/doc/ci/secrets/azure_key_vault.md b/doc/ci/secrets/azure_key_vault.md index 03515417827..8cd3c375b05 100644 --- a/doc/ci/secrets/azure_key_vault.md +++ b/doc/ci/secrets/azure_key_vault.md @@ -81,7 +81,7 @@ Caller is not authorized to perform action on resource.\r\nIf role assignments, ForbiddenByRbac ``` -If your Azure Key Vault is using RBAC, you must add the **Key Vault Secrets User** to your Azure AD +If your Azure Key Vault is using RBAC, you must add the **Key Vault Secrets User** role assignment to your Azure AD application. For example: diff --git a/doc/ci/testing/browser_performance_testing.md b/doc/ci/testing/browser_performance_testing.md index d8c66c2d4d5..23e8cf80d74 100644 --- a/doc/ci/testing/browser_performance_testing.md +++ b/doc/ci/testing/browser_performance_testing.md @@ -49,7 +49,8 @@ If the Browser Performance report has no data to compare, such as when you add t Browser Performance job in your `.gitlab-ci.yml` for the very first time, the Browser Performance report widget doesn't display. It must have run at least once on the target branch (`main`, for example), before it displays in a -merge request targeting that branch. +merge request targeting that branch. Additionally, the widget only displays if the +job ran in the latest pipeline for the Merge request. ![Browser Performance Widget](img/browser_performance_testing.png) diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md index aa736884529..7e300f507cf 100644 --- a/doc/ci/yaml/index.md +++ b/doc/ci/yaml/index.md @@ -497,6 +497,7 @@ workflow: - if: '$CI_MERGE_REQUEST_LABELS =~ /pipeline:run-in-ruby3/' variables: PROJECT1_PIPELINE_NAME: 'Ruby 3 pipeline' + - when: always # Other pipelines can run, but use the default name ``` **Additional details**: