diff --git a/data/nav.yml b/data/nav.yml index 843de24d6d..af5c89599f 100644 --- a/data/nav.yml +++ b/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: diff --git a/pages/package_registries/security.md b/pages/package_registries/security.md index d417be15e7..8d34d769b8 100644 --- a/pages/package_registries/security.md +++ b/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. diff --git a/pages/package_registries/security/slsa_provenance.md b/pages/package_registries/security/slsa_provenance.md index b2964e1ee1..1fc70acae8 100644 --- a/pages/package_registries/security/slsa_provenance.md +++ b/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. diff --git a/pages/platform.md b/pages/platform.md index ec2fbb34a6..da77c2e5d3 100644 --- a/pages/platform.md +++ b/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. diff --git a/pages/platform/service_quotas.md b/pages/platform/service_quotas.md new file mode 100644 index 0000000000..8f4cae79aa --- /dev/null +++ b/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. + +
Service quota type | +Description and default limit | +
---|---|
+ <%= quota[:title] %> + | +
+ <%= quota[:description] %> + Default: <%= quota[:default_value] %> + |
+