Skip to content

Add CI/CD default artifact expiration time for SaaS to pricing FAQs

Michael Friedrich requested to merge pricing-faq-add-artifact-default-expiration-policy into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

@joshlambert @jreporter pointed out that the default job artifact expiration policy on GitLab.com SaaS is set to 30 days, when not specified in the CI/CD configuration. I somehow remembered this but was not sure.

To help our users better understand the actions to take, this MR adds a note and URL to the default expiration time in the pricing FAQs for the free and paid tier.

The FAQ links to generic docs items where the difference between self-managed and SaaS is not explained. Therefore, the FAQ can be the SSoT, explaining the default limit and linking the resources together.

Context in https://gitlab.com/groups/gitlab-org/-/epics/10940#note_1539875507

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

cc @ipedowitz

Merge request reports