Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in reason, fix links #746

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 9 additions & 8 deletions docs/build.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. |
Expand Down Expand Up @@ -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:

Expand Down