Merge pull request #84 from buildkite/docs-public-pr-2774

Add Pipelines product 'Service Quotas' page

data/nav.yml

@@ -593,6 +593,8 @@
           path: "integrations/sso/custom-saml"
         - name: "Set up with GraphQL"
           path: "integrations/sso/sso-setup-with-graphql"
+    - name: "Service quotas"
+      path: "platform/service-quotas"
 - name: "APIs"
   path: "apis"
   children:

pages/package_registries/security.md

@@ -10,3 +10,4 @@ This section contains the following topics:
 
 - [OIDC with Buildkite Package Registries](/docs/package-registries/security/oidc) and how to restrict access to registries through OIDC policies.
 - [User, team, and registry permissions](/docs/package-registries/security/permissions) and how to manage team and user access to registries.
+- [SLSA provenance](/docs/package-registries/security/slsa-provenance) and how to publish packages and other artifact types to registries with SLSA provenance.

pages/package_registries/security/slsa_provenance.md

@@ -1,7 +1,5 @@
 # Generate and store SLSA provenance
 
-## Introduction
-
 Supply-chain levels for software artifacts ([SLSA](https://slsa.dev/spec/) and pronounced like "salsa") is an industry-consensus specification for describing and gradually improving artifact supply chain security.
 
 When using Buildkite [Pipelines](/docs/pipelines) with [Package Registries](/docs/package-registries), you can publish software packages and artifacts to registries with [SLSA provenance](https://slsa.dev/provenance) in only four steps.

pages/platform.md

@@ -13,3 +13,5 @@ The Buildkite platform documentation contains docs for _platform_-level features
 - [Buildkite CLI](/docs/cli), which provides command line/terminal access to work with features across the Buildkite platform.
 
 - [Single sign-on (SSO)](/docs/integrations/sso), with guidelines on how to protect access to your Buildkite organization using a supported third-party SSO provider.
+
+- [Service quotas](/docs/platform/service-quotas), lists Buildkite's default service quota values and how you can alter these if required.

pages/platform/service_quotas.md

@@ -0,0 +1,102 @@
+---
+toc: false
+---
+
+# Service quotas
+
+Service quotas are put in place to ensure that Buildkite can provide a reliable service to all customers. These quotas are scoped to your organization, and can be increased by emailing Support at [support@buildkite.com](mailto:support@buildkite.com) and providing details about your use case.
+
+The following table lists Buildkite's default service quota values.
+
+<table>
+  <thead>
+    <tr>
+      <th style="width:25%">Service quota type</th>
+      <th style="width:75%">Description and default limit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <% [
+      {
+        title: "Invitations per organization",
+        description: "The maximum number of pending invitations for an organization.",
+        default_value: "20 invitations"
+      },
+      {
+        title: "REST API rate limit per organization",
+        description: "The number of requests an organization can make to Organization endpoints on the REST API, per minute.",
+        default_value: "200 requests/min"
+      },
+      {
+        title: "Slack services per organization",
+        description: "The maximum number of Slack services that can be added to an organization.",
+        default_value: "50 services"
+      },
+      {
+        title: "Teams per organization",
+        description: "The maximum number of teams that an organization can have.",
+        default_value: "250 teams"
+      },
+      {
+        title: "Webhook services per organization",
+        description: "The maximum number of Webhook services that can be added to an organization.",
+        default_value: "15 services"
+      },
+      {
+        title: "Artifact retention",
+        description: "The maximum time we'll store artifacts for, in days, before assuming it has been deleted by an S3 Lifecycle rule, which must be configured separately.",
+        default_value: "180 days"
+      },
+      {
+        title: "Jobs per build",
+        description: "The maximum number of jobs that can be created in a single pipeline build (including job retries).",
+        default_value: "4,000 jobs"
+      },
+      {
+        title: "Jobs created per pipeline upload",
+        description: "The maximum number of jobs that can be created in a single pipeline upload.",
+        default_value: "500 jobs"
+      },
+      {
+        title: "Pipeline uploads per build",
+        description: "The maximum number of pipeline uploads that can be performed in a single build.",
+        default_value: "500 pipeline uploads"
+      },
+      {
+        title: "Trigger build depth per pipeline",
+        description: "The maximum depth of a chain of trigger builds.",
+        default_value: "10 builds"
+      },
+      {
+        title: "Artifacts per job",
+        description: "The maximum number of artifacts that can be uploaded to Buildkite per job.",
+        default_value: "250,000 artifacts"
+      },
+      {
+        title: "Artifact file size",
+        description: "The maximum size of an artifact that can be uploaded to Buildkite from an agent.",
+        default_value: "10 GiB"
+      },
+      {
+        title: "Artifact batch total file size",
+        description: "The maximum cumulative size of artifacts that can be uploaded to Buildkite from an agent in a single job using the <code>buildkite-agent artifact upload</code> command.",
+        default_value: "50 GiB"
+      },
+      {
+        title: "Log size per job",
+        description: "The maximum file-size of a job's log (uploaded by an agent to Buildkite in chunks).",
+        default_value: "1,024 MiB"
+      }
+    ].sort_by { |quota| quota[:title] }.each do |quota| %>
+      <tr>
+        <td>
+          <strong><%= quota[:title] %></strong>
+         </td>
+        <td>
+          <p><%= quota[:description] %></p>
+          Default: <strong><%= quota[:default_value] %></strong>
+        </td>
+      </tr>
+    <% end %>
+  </tbody>
+</table>