From c2126af7ada29743bf020ac814aedf0f74725876 Mon Sep 17 00:00:00 2001 From: Sascha Schwarze Date: Wed, 28 Apr 2021 13:30:23 +0200 Subject: [PATCH] Fix typo in reason, fix links --- docs/build.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/build.md b/docs/build.md index b34179a99..b3cc6c326 100644 --- a/docs/build.md +++ b/docs/build.md @@ -48,12 +48,12 @@ In order to prevent users from triggering `BuildRuns` (_execution of a Build_) t | Status.Reason | Description | | --- | --- | -| BuildStrategyNotFound | The referenced namespace-scope strategy doesn´t exist. | -| ClusterBuildStrategyNotFound | The referenced cluster-scope strategy doesn´t exist. | +| BuildStrategyNotFound | The referenced namespace-scope strategy doesn't exist. | +| ClusterBuildStrategyNotFound | The referenced cluster-scope strategy doesn't exist. | | SetOwnerReferenceFailed | Setting ownerreferences between a Build and a BuildRun failed. This is triggered when making use of the `build.shipwright.io/build-run-deletion` annotation in a Build. | -| SpecSourceSecretNotFound | The secret used to authenticate to git doesn´t exist. | -| SpecOutputSecretRefNotFound | The secret used to authenticate to the container registry doesn´t exist. | -| SpecBuilderSecretRefNotFound | The secret used to authenticate to the container registry doesn´t exist.| +| SpecSourceSecretRefNotFound | The secret used to authenticate to git doesn't exist. | +| SpecOutputSecretRefNotFound | The secret used to authenticate to the container registry doesn't exist. | +| SpecBuilderSecretRefNotFound | The secret used to authenticate to the container registry doesn't exist.| | MultipleSecretRefNotFound | More than one secret is missing. At the moment, only three paths on a Build can specify a secret. | | RuntimePathsCanNotBeEmpty | The Runtime feature is used, but the runtime path was not defined. This is mandatory. | | RemoteRepositoryUnreachable | The defined `spec.source.url` was not found. This validation only take place for http/https protocols. | @@ -151,11 +151,12 @@ spec: A `Build` resource can specify the `BuildStrategy` to use, these are: -- [Source-to-Image](buildstrategies.md#source-to-image) -- [Buildpacks-v3](buildstrategies.md#buildpacks-v3) - [Buildah](buildstrategies.md#buildah) +- [Buildpacks-v3](buildstrategies.md#buildpacks-v3) +- [BuildKit](buildstrategies.md#buildkit) - [Kaniko](buildstrategies.md#kaniko) -* [ko](docs/buildstrategies.md#ko) +- [ko](buildstrategies.md#ko) +- [Source-to-Image](buildstrategies.md#source-to-image) Defining the strategy is straightforward, you need to define the `name` and the `kind`. For example: