Specify 5MB limit for consuming artifacts
What does this MR do?
Specify that there is currently a 5MB hard-coded artifact size limit when an artifact is consumed by a job.
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
added docsimprovement documentation typemaintenance labels
assigned to @jfarmiloe
added Support Team Contributions label
marked the checklist item Optional. Consider taking the GitLab Technical Writing Fundamentals course. as completed
marked the checklist item If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. as completed
requested review from @marcel.amirault
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @rspeicher
,@eread
,@aqualls
,@alyubenkov
,@rdickenson
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
Edited by GitLab Reviewer-Recommender Bot- Resolved by Justin Farmiloe
Hi @marcel.amirault - could you please review my MR - thanks!
1 Warning This merge request does not refer to an existing milestone. 1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/ci/pipelines/parent_child_pipelines.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Generated by
Dangerrequested review from @fabiopitino and removed review request for @marcel.amirault
added Technical Writing devopsverify grouppipeline execution labels
added sectionops label
- Resolved by Marcel Amirault
requested review from @marcel.amirault and removed review request for @fabiopitino
mentioned in issue #249140
removed review request for @marcel.amirault
requested review from @marcel.amirault
@jfarmiloe Thanks a lot, LGTM!
enabled an automatic merge when the pipeline for 64ed7bb6 succeeds
mentioned in commit ed6d6571
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
mentioned in issue gitlab-com/support/support-team-meta#4291 (closed)
added releasedpublished label
added releasedcandidate label and removed releasedpublished label