Skip to content
Snippets Groups Projects

Docs: fix artifacts size limit description

What does this MR do?

This MR fixes a detail on the documentation of artifacts max size limit. Artifacts size limits are based on compressed size, not uncompressed size as the docs state.

Demo

Link to artifact whose size is 1.5 GiB

The demo pipeline creates 3 separate jobs, each one that generates a 1.5 GiB file with:

  • zeros
  • 0x0A (\n)
  • pseudorandom data

The pipeline shows that the first two jobs (zeros, 0x0A) passes. The compressed size of the artifacts is around 1.5 MB (uncompressed size: 1.5 GiB). For the third job (pseudorandom data), the compressed size is > 1 GiB and the job fails.

Because the first two jobs pass, the max artifacts size limit is on the compressed size, not the uncompressed size.

Author's checklist (required)

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
    • Ensure docs metadata are present and up-to-date.
    • Ensure Technical Writing and documentation are added.
    • Add the corresponding docs:: scoped label.
    • Add twdoing when starting work on the MR.
    • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Jonston Chan

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading