Chapter 2. BuildConfig [build.openshift.io/v1]
- Description
Build configurations define a build process for new container images. There are three types of builds possible - a container image build using a Dockerfile, a Source-to-Image build that uses a specially prepared base image that accepts source code that it can make runnable, and a custom build that can run // arbitrary container images as a base and accept the build parameters. Builds run on the cluster and on completion are pushed to the container image registry specified in the "output" section. A build can be triggered via a webhook, when the base image changes, or when a user manually requests a new build be // created.
Each build created by a build configuration is numbered and refers back to its parent configuration. Multiple builds can be triggered at once. Builds that do not have "output" set can be used to test code or run a verification build.
Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
- Type
-
object
- Required
-
spec
-
2.1. Specification
Property | Type | Description |
---|---|---|
|
| APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
| Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
| ||
|
| BuildConfigSpec describes when and how builds are created |
|
| BuildConfigStatus contains current state of the build config object. |
2.1.1. .spec
- Description
- BuildConfigSpec describes when and how builds are created
- Type
-
object
- Required
-
strategy
-
Property | Type | Description |
---|---|---|
|
| completionDeadlineSeconds is an optional duration in seconds, counted from the time when a build pod gets scheduled in the system, that the build may be active on a node before the system actively tries to terminate the build; value must be positive integer |
|
| failedBuildsHistoryLimit is the number of old failed builds to retain. When a BuildConfig is created, the 5 most recent failed builds are retained unless this value is set. If removed after the BuildConfig has been created, all failed builds are retained. |
|
| mountTrustedCA bind mounts the cluster’s trusted certificate authorities, as defined in the cluster’s proxy configuration, into the build. This lets processes within a build trust components signed by custom PKI certificate authorities, such as private artifact repositories and HTTPS proxies.
When this field is set to true, the contents of |
|
| nodeSelector is a selector which must be true for the build pod to fit on a node If nil, it can be overridden by default build nodeselector values for the cluster. If set to an empty map or a map with any values, default build nodeselector values are ignored. |
|
| BuildOutput is input to a build strategy and describes the container image that the strategy should produce. |
|
| A BuildPostCommitSpec holds a build post commit hook specification. The hook executes a command in a temporary container running the build output image, immediately after the last layer of the image is committed and before the image is pushed to a registry. The command is executed with the current working directory ($PWD) set to the image’s WORKDIR. The build will be marked as failed if the hook execution fails. It will fail if the script or command return a non-zero exit code, or if there is any other error related to starting the temporary container.
There are five different ways to configure the hook. As an example, all forms below are equivalent and will execute 1. Shell script: "postCommit": { "script": "rake test --verbose", } The above is a convenient form which is equivalent to: "postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] } 2. A command as the image entrypoint: "postCommit": { "commit": ["rake", "test", "--verbose"] } Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint. 3. Pass arguments to the default entrypoint: "postCommit": { "args": ["rake", "test", "--verbose"] } This form is only useful if the image entrypoint can handle arguments. 4. Shell script with arguments: "postCommit": { "script": "rake test $1", "args": ["--verbose"] } This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, $0 will be "/bin/sh" and $1, $2, etc, are the positional arguments from Args. 5. Command with arguments: "postCommit": { "command": ["rake", "test"], "args": ["--verbose"] } This form is equivalent to appending the arguments to the Command slice. It is invalid to provide both Script and Command simultaneously. If none of the fields are specified, the hook is not executed. |
| resources computes resource requirements to execute the build. | |
|
| SourceRevision is the revision or commit information from the source for the build |
|
| RunPolicy describes how the new build created from this build configuration will be scheduled for execution. This is optional, if not specified we default to "Serial". |
|
| serviceAccount is the name of the ServiceAccount to use to run the pod created by this build. The pod will be allowed to use secrets referenced by the ServiceAccount |
|
| BuildSource is the SCM used for the build. |
|
| BuildStrategy contains the details of how to perform a build. |
|
| successfulBuildsHistoryLimit is the number of old successful builds to retain. When a BuildConfig is created, the 5 most recent successful builds are retained unless this value is set. If removed after the BuildConfig has been created, all successful builds are retained. |
|
| triggers determine how new Builds can be launched from a BuildConfig. If no triggers are defined, a new build can only occur as a result of an explicit client build creation. |
|
| BuildTriggerPolicy describes a policy for a single trigger that results in a new Build. |
2.1.2. .spec.output
- Description
- BuildOutput is input to a build strategy and describes the container image that the strategy should produce.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| imageLabels define a list of labels that are applied to the resulting image. If there are multiple labels with the same name then the last one in the list is used. |
|
| ImageLabel represents a label applied to the resulting image. |
| PushSecret is the name of a Secret that would be used for setting up the authentication for executing the Docker push to authentication enabled Docker Registry (or Docker Hub). | |
| to defines an optional location to push the output of this build to. Kind must be one of 'ImageStreamTag' or 'DockerImage'. This value will be used to look up a container image repository to push to. In the case of an ImageStreamTag, the ImageStreamTag will be looked for in the namespace of the build unless Namespace is specified. |
2.1.3. .spec.output.imageLabels
- Description
- imageLabels define a list of labels that are applied to the resulting image. If there are multiple labels with the same name then the last one in the list is used.
- Type
-
array
2.1.4. .spec.output.imageLabels[]
- Description
- ImageLabel represents a label applied to the resulting image.
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| name defines the name of the label. It must have non-zero length. |
|
| value defines the literal value of the label. |
2.1.5. .spec.postCommit
- Description
A BuildPostCommitSpec holds a build post commit hook specification. The hook executes a command in a temporary container running the build output image, immediately after the last layer of the image is committed and before the image is pushed to a registry. The command is executed with the current working directory ($PWD) set to the image’s WORKDIR.
The build will be marked as failed if the hook execution fails. It will fail if the script or command return a non-zero exit code, or if there is any other error related to starting the temporary container.
There are five different ways to configure the hook. As an example, all forms below are equivalent and will execute
rake test --verbose
.Shell script:
"postCommit": { "script": "rake test --verbose", }
The above is a convenient form which is equivalent to:
"postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] }
A command as the image entrypoint:
"postCommit": { "commit": ["rake", "test", "--verbose"] }
Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint.
Pass arguments to the default entrypoint:
"postCommit": { "args": ["rake", "test", "--verbose"] }
This form is only useful if the image entrypoint can handle arguments.
Shell script with arguments:
"postCommit": { "script": "rake test $1", "args": ["--verbose"] }
This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, $0 will be "/bin/sh" and $1, $2, etc, are the positional arguments from Args.
Command with arguments:
"postCommit": { "command": ["rake", "test"], "args": ["--verbose"] }
This form is equivalent to appending the arguments to the Command slice.
It is invalid to provide both Script and Command simultaneously. If none of the fields are specified, the hook is not executed.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| args is a list of arguments that are provided to either Command, Script or the container image’s default entrypoint. The arguments are placed immediately after the command to be run. |
|
|
command is the command to run. It may not be specified with Script. This might be needed if the image doesn’t have |
|
|
script is a shell script to be run with |
2.1.6. .spec.revision
- Description
- SourceRevision is the revision or commit information from the source for the build
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| GitSourceRevision is the commit information from a git source for a build |
|
| type of the build source, may be one of 'Source', 'Dockerfile', 'Binary', or 'Images' |
2.1.7. .spec.revision.git
- Description
- GitSourceRevision is the commit information from a git source for a build
- Type
-
object
Property | Type | Description |
---|---|---|
|
| SourceControlUser defines the identity of a user of source control |
|
| commit is the commit hash identifying a specific commit |
|
| SourceControlUser defines the identity of a user of source control |
|
| message is the description of a specific commit |
2.1.8. .spec.revision.git.author
- Description
- SourceControlUser defines the identity of a user of source control
- Type
-
object
Property | Type | Description |
---|---|---|
|
| email of the source control user |
|
| name of the source control user |
2.1.9. .spec.revision.git.committer
- Description
- SourceControlUser defines the identity of a user of source control
- Type
-
object
Property | Type | Description |
---|---|---|
|
| email of the source control user |
|
| name of the source control user |
2.1.10. .spec.source
- Description
- BuildSource is the SCM used for the build.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| BinaryBuildSource describes a binary file to be used for the Docker and Source build strategies, where the file will be extracted and used as the build source. |
|
| configMaps represents a list of configMaps and their destinations that will be used for the build. |
|
| ConfigMapBuildSource describes a configmap and its destination directory that will be used only at the build time. The content of the configmap referenced here will be copied into the destination directory instead of mounting. |
|
| contextDir specifies the sub-directory where the source code for the application exists. This allows to have buildable sources in directory other than root of repository. |
|
| dockerfile is the raw contents of a Dockerfile which should be built. When this option is specified, the FROM may be modified based on your strategy base image and additional ENV stanzas from your strategy environment will be added after the FROM, but before the rest of your Dockerfile stanzas. The Dockerfile source type may be used with other options like git - in those cases the Git repo will have any innate Dockerfile replaced in the context dir. |
|
| GitBuildSource defines the parameters of a Git SCM |
|
| images describes a set of images to be used to provide source for the build |
|
| ImageSource is used to describe build source that will be extracted from an image or used during a multi stage build. A reference of type ImageStreamTag, ImageStreamImage or DockerImage may be used. A pull secret can be specified to pull the image from an external registry or override the default service account secret if pulling from the internal registry. Image sources can either be used to extract content from an image and place it into the build context along with the repository source, or used directly during a multi-stage container image build to allow content to be copied without overwriting the contents of the repository source (see the 'paths' and 'as' fields). |
|
| secrets represents a list of secrets and their destinations that will be used only for the build. |
|
| SecretBuildSource describes a secret and its destination directory that will be used only at the build time. The content of the secret referenced here will be copied into the destination directory instead of mounting. |
| sourceSecret is the name of a Secret that would be used for setting up the authentication for cloning private repository. The secret contains valid credentials for remote repository, where the data’s key represent the authentication method to be used and value is the base64 encoded credentials. Supported auth methods are: ssh-privatekey. | |
|
| type of build input to accept |
2.1.11. .spec.source.binary
- Description
- BinaryBuildSource describes a binary file to be used for the Docker and Source build strategies, where the file will be extracted and used as the build source.
- Type
-
object
Property | Type | Description |
---|---|---|
|
|
asFile indicates that the provided binary input should be considered a single file within the build input. For example, specifying "webapp.war" would place the provided binary as |
2.1.12. .spec.source.configMaps
- Description
- configMaps represents a list of configMaps and their destinations that will be used for the build.
- Type
-
array
2.1.13. .spec.source.configMaps[]
- Description
- ConfigMapBuildSource describes a configmap and its destination directory that will be used only at the build time. The content of the configmap referenced here will be copied into the destination directory instead of mounting.
- Type
-
object
- Required
-
configMap
-
Property | Type | Description |
---|---|---|
| configMap is a reference to an existing configmap that you want to use in your build. | |
|
| destinationDir is the directory where the files from the configmap should be available for the build time. For the Source build strategy, these will be injected into a container where the assemble script runs. For the container image build strategy, these will be copied into the build directory, where the Dockerfile is located, so users can ADD or COPY them during container image build. |
2.1.14. .spec.source.git
- Description
- GitBuildSource defines the parameters of a Git SCM
- Type
-
object
- Required
-
uri
-
Property | Type | Description |
---|---|---|
|
| httpProxy is a proxy used to reach the git repository over http |
|
| httpsProxy is a proxy used to reach the git repository over https |
|
| noProxy is the list of domains for which the proxy should not be used |
|
| ref is the branch/tag/ref to build. |
|
| uri points to the source that will be built. The structure of the source will depend on the type of build to run |
2.1.15. .spec.source.images
- Description
- images describes a set of images to be used to provide source for the build
- Type
-
array
2.1.16. .spec.source.images[]
- Description
- ImageSource is used to describe build source that will be extracted from an image or used during a multi stage build. A reference of type ImageStreamTag, ImageStreamImage or DockerImage may be used. A pull secret can be specified to pull the image from an external registry or override the default service account secret if pulling from the internal registry. Image sources can either be used to extract content from an image and place it into the build context along with the repository source, or used directly during a multi-stage container image build to allow content to be copied without overwriting the contents of the repository source (see the 'paths' and 'as' fields).
- Type
-
object
- Required
-
from
-
Property | Type | Description |
---|---|---|
|
| A list of image names that this source will be used in place of during a multi-stage container image build. For instance, a Dockerfile that uses "COPY --from=nginx:latest" will first check for an image source that has "nginx:latest" in this field before attempting to pull directly. If the Dockerfile does not reference an image source it is ignored. This field and paths may both be set, in which case the contents will be used twice. |
| from is a reference to an ImageStreamTag, ImageStreamImage, or DockerImage to copy source from. | |
|
| paths is a list of source and destination paths to copy from the image. This content will be copied into the build context prior to starting the build. If no paths are set, the build context will not be altered. |
|
| ImageSourcePath describes a path to be copied from a source image and its destination within the build directory. |
| pullSecret is a reference to a secret to be used to pull the image from a registry If the image is pulled from the OpenShift registry, this field does not need to be set. |
2.1.17. .spec.source.images[].paths
- Description
- paths is a list of source and destination paths to copy from the image. This content will be copied into the build context prior to starting the build. If no paths are set, the build context will not be altered.
- Type
-
array
2.1.18. .spec.source.images[].paths[]
- Description
- ImageSourcePath describes a path to be copied from a source image and its destination within the build directory.
- Type
-
object
- Required
-
sourcePath
-
destinationDir
-
Property | Type | Description |
---|---|---|
|
| destinationDir is the relative directory within the build directory where files copied from the image are placed. |
|
| sourcePath is the absolute path of the file or directory inside the image to copy to the build directory. If the source path ends in /. then the content of the directory will be copied, but the directory itself will not be created at the destination. |
2.1.19. .spec.source.secrets
- Description
- secrets represents a list of secrets and their destinations that will be used only for the build.
- Type
-
array
2.1.20. .spec.source.secrets[]
- Description
- SecretBuildSource describes a secret and its destination directory that will be used only at the build time. The content of the secret referenced here will be copied into the destination directory instead of mounting.
- Type
-
object
- Required
-
secret
-
Property | Type | Description |
---|---|---|
|
| destinationDir is the directory where the files from the secret should be available for the build time. For the Source build strategy, these will be injected into a container where the assemble script runs. Later, when the script finishes, all files injected will be truncated to zero length. For the container image build strategy, these will be copied into the build directory, where the Dockerfile is located, so users can ADD or COPY them during container image build. |
| secret is a reference to an existing secret that you want to use in your build. |
2.1.21. .spec.strategy
- Description
- BuildStrategy contains the details of how to perform a build.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| CustomBuildStrategy defines input parameters specific to Custom build. |
|
| DockerBuildStrategy defines input parameters specific to container image build. |
|
| JenkinsPipelineBuildStrategy holds parameters specific to a Jenkins Pipeline build. Deprecated: use OpenShift Pipelines |
|
| SourceBuildStrategy defines input parameters specific to an Source build. |
|
| type is the kind of build strategy. |
2.1.22. .spec.strategy.customStrategy
- Description
- CustomBuildStrategy defines input parameters specific to Custom build.
- Type
-
object
- Required
-
from
-
Property | Type | Description |
---|---|---|
|
| buildAPIVersion is the requested API version for the Build object serialized and passed to the custom builder |
| env contains additional environment variables you want to pass into a builder container. | |
|
| exposeDockerSocket will allow running Docker commands (and build container images) from inside the container. |
|
| forcePull describes if the controller should configure the build pod to always pull the images for the builder or only pull if it is not present locally |
| from is reference to an DockerImage, ImageStreamTag, or ImageStreamImage from which the container image should be pulled | |
| pullSecret is the name of a Secret that would be used for setting up the authentication for pulling the container images from the private Docker registries | |
|
| secrets is a list of additional secrets that will be included in the build pod |
|
| SecretSpec specifies a secret to be included in a build pod and its corresponding mount point |
2.1.23. .spec.strategy.customStrategy.secrets
- Description
- secrets is a list of additional secrets that will be included in the build pod
- Type
-
array
2.1.24. .spec.strategy.customStrategy.secrets[]
- Description
- SecretSpec specifies a secret to be included in a build pod and its corresponding mount point
- Type
-
object
- Required
-
secretSource
-
mountPath
-
Property | Type | Description |
---|---|---|
|
| mountPath is the path at which to mount the secret |
| secretSource is a reference to the secret |
2.1.25. .spec.strategy.dockerStrategy
- Description
- DockerBuildStrategy defines input parameters specific to container image build.
- Type
-
object
Property | Type | Description |
---|---|---|
| buildArgs contains build arguments that will be resolved in the Dockerfile. See https://docs.docker.com/engine/reference/builder/#/arg for more details. NOTE: Only the 'name' and 'value' fields are supported. Any settings on the 'valueFrom' field are ignored. | |
|
|
dockerfilePath is the path of the Dockerfile that will be used to build the container image, relative to the root of the context (contextDir). Defaults to |
| env contains additional environment variables you want to pass into a builder container. | |
|
| forcePull describes if the builder should pull the images from registry prior to building. |
| from is a reference to an DockerImage, ImageStreamTag, or ImageStreamImage which overrides the FROM image in the Dockerfile for the build. If the Dockerfile uses multi-stage builds, this will replace the image in the last FROM directive of the file. | |
|
| imageOptimizationPolicy describes what optimizations the system can use when building images to reduce the final size or time spent building the image. The default policy is 'None' which means the final build image will be equivalent to an image created by the container image build API. The experimental policy 'SkipLayers' will avoid commiting new layers in between each image step, and will fail if the Dockerfile cannot provide compatibility with the 'None' policy. An additional experimental policy 'SkipLayersAndWarn' is the same as 'SkipLayers' but simply warns if compatibility cannot be preserved. |
|
| noCache if set to true indicates that the container image build must be executed with the --no-cache=true flag |
| pullSecret is the name of a Secret that would be used for setting up the authentication for pulling the container images from the private Docker registries | |
|
| volumes is a list of input volumes that can be mounted into the builds runtime environment. Only a subset of Kubernetes Volume sources are supported by builds. More info: https://kubernetes.io/docs/concepts/storage/volumes |
|
| BuildVolume describes a volume that is made available to build pods, such that it can be mounted into buildah’s runtime environment. Only a subset of Kubernetes Volume sources are supported. |
2.1.26. .spec.strategy.dockerStrategy.volumes
- Description
- volumes is a list of input volumes that can be mounted into the builds runtime environment. Only a subset of Kubernetes Volume sources are supported by builds. More info: https://kubernetes.io/docs/concepts/storage/volumes
- Type
-
array
2.1.27. .spec.strategy.dockerStrategy.volumes[]
- Description
- BuildVolume describes a volume that is made available to build pods, such that it can be mounted into buildah’s runtime environment. Only a subset of Kubernetes Volume sources are supported.
- Type
-
object
- Required
-
name
-
source
-
mounts
-
Property | Type | Description |
---|---|---|
|
| mounts represents the location of the volume in the image build container |
|
| BuildVolumeMount describes the mounting of a Volume within buildah’s runtime environment. |
|
| name is a unique identifier for this BuildVolume. It must conform to the Kubernetes DNS label standard and be unique within the pod. Names that collide with those added by the build controller will result in a failed build with an error message detailing which name caused the error. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names |
|
| BuildVolumeSource represents the source of a volume to mount Only one of its supported types may be specified at any given time. |
2.1.28. .spec.strategy.dockerStrategy.volumes[].mounts
- Description
- mounts represents the location of the volume in the image build container
- Type
-
array
2.1.29. .spec.strategy.dockerStrategy.volumes[].mounts[]
- Description
- BuildVolumeMount describes the mounting of a Volume within buildah’s runtime environment.
- Type
-
object
- Required
-
destinationPath
-
Property | Type | Description |
---|---|---|
|
| destinationPath is the path within the buildah runtime environment at which the volume should be mounted. The transient mount within the build image and the backing volume will both be mounted read only. Must be an absolute path, must not contain '..' or ':', and must not collide with a destination path generated by the builder process Paths that collide with those added by the build controller will result in a failed build with an error message detailing which path caused the error. |
2.1.30. .spec.strategy.dockerStrategy.volumes[].source
- Description
- BuildVolumeSource represents the source of a volume to mount Only one of its supported types may be specified at any given time.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
| configMap represents a ConfigMap that should populate this volume | |
| csi represents ephemeral storage provided by external CSI drivers which support this capability | |
| secret represents a Secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret | |
|
| type is the BuildVolumeSourceType for the volume source. Type must match the populated volume source. Valid types are: Secret, ConfigMap |
2.1.31. .spec.strategy.jenkinsPipelineStrategy
- Description
- JenkinsPipelineBuildStrategy holds parameters specific to a Jenkins Pipeline build. Deprecated: use OpenShift Pipelines
- Type
-
object
Property | Type | Description |
---|---|---|
| env contains additional environment variables you want to pass into a build pipeline. | |
|
| Jenkinsfile defines the optional raw contents of a Jenkinsfile which defines a Jenkins pipeline build. |
|
| JenkinsfilePath is the optional path of the Jenkinsfile that will be used to configure the pipeline relative to the root of the context (contextDir). If both JenkinsfilePath & Jenkinsfile are both not specified, this defaults to Jenkinsfile in the root of the specified contextDir. |
2.1.32. .spec.strategy.sourceStrategy
- Description
- SourceBuildStrategy defines input parameters specific to an Source build.
- Type
-
object
- Required
-
from
-
Property | Type | Description |
---|---|---|
| env contains additional environment variables you want to pass into a builder container. | |
|
| forcePull describes if the builder should pull the images from registry prior to building. |
| from is reference to an DockerImage, ImageStreamTag, or ImageStreamImage from which the container image should be pulled | |
|
| incremental flag forces the Source build to do incremental builds if true. |
| pullSecret is the name of a Secret that would be used for setting up the authentication for pulling the container images from the private Docker registries | |
|
| scripts is the location of Source scripts |
|
| volumes is a list of input volumes that can be mounted into the builds runtime environment. Only a subset of Kubernetes Volume sources are supported by builds. More info: https://kubernetes.io/docs/concepts/storage/volumes |
|
| BuildVolume describes a volume that is made available to build pods, such that it can be mounted into buildah’s runtime environment. Only a subset of Kubernetes Volume sources are supported. |
2.1.33. .spec.strategy.sourceStrategy.volumes
- Description
- volumes is a list of input volumes that can be mounted into the builds runtime environment. Only a subset of Kubernetes Volume sources are supported by builds. More info: https://kubernetes.io/docs/concepts/storage/volumes
- Type
-
array
2.1.34. .spec.strategy.sourceStrategy.volumes[]
- Description
- BuildVolume describes a volume that is made available to build pods, such that it can be mounted into buildah’s runtime environment. Only a subset of Kubernetes Volume sources are supported.
- Type
-
object
- Required
-
name
-
source
-
mounts
-
Property | Type | Description |
---|---|---|
|
| mounts represents the location of the volume in the image build container |
|
| BuildVolumeMount describes the mounting of a Volume within buildah’s runtime environment. |
|
| name is a unique identifier for this BuildVolume. It must conform to the Kubernetes DNS label standard and be unique within the pod. Names that collide with those added by the build controller will result in a failed build with an error message detailing which name caused the error. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names |
|
| BuildVolumeSource represents the source of a volume to mount Only one of its supported types may be specified at any given time. |
2.1.35. .spec.strategy.sourceStrategy.volumes[].mounts
- Description
- mounts represents the location of the volume in the image build container
- Type
-
array
2.1.36. .spec.strategy.sourceStrategy.volumes[].mounts[]
- Description
- BuildVolumeMount describes the mounting of a Volume within buildah’s runtime environment.
- Type
-
object
- Required
-
destinationPath
-
Property | Type | Description |
---|---|---|
|
| destinationPath is the path within the buildah runtime environment at which the volume should be mounted. The transient mount within the build image and the backing volume will both be mounted read only. Must be an absolute path, must not contain '..' or ':', and must not collide with a destination path generated by the builder process Paths that collide with those added by the build controller will result in a failed build with an error message detailing which path caused the error. |
2.1.37. .spec.strategy.sourceStrategy.volumes[].source
- Description
- BuildVolumeSource represents the source of a volume to mount Only one of its supported types may be specified at any given time.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
| configMap represents a ConfigMap that should populate this volume | |
| csi represents ephemeral storage provided by external CSI drivers which support this capability | |
| secret represents a Secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret | |
|
| type is the BuildVolumeSourceType for the volume source. Type must match the populated volume source. Valid types are: Secret, ConfigMap |
2.1.38. .spec.triggers
- Description
- triggers determine how new Builds can be launched from a BuildConfig. If no triggers are defined, a new build can only occur as a result of an explicit client build creation.
- Type
-
array
2.1.39. .spec.triggers[]
- Description
- BuildTriggerPolicy describes a policy for a single trigger that results in a new Build.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| WebHookTrigger is a trigger that gets invoked using a webhook type of post |
|
| WebHookTrigger is a trigger that gets invoked using a webhook type of post |
|
| WebHookTrigger is a trigger that gets invoked using a webhook type of post |
|
| WebHookTrigger is a trigger that gets invoked using a webhook type of post |
|
| ImageChangeTrigger allows builds to be triggered when an ImageStream changes |
|
| type is the type of build trigger. Valid values: - GitHub GitHubWebHookBuildTriggerType represents a trigger that launches builds on GitHub webhook invocations - Generic GenericWebHookBuildTriggerType represents a trigger that launches builds on generic webhook invocations - GitLab GitLabWebHookBuildTriggerType represents a trigger that launches builds on GitLab webhook invocations - Bitbucket BitbucketWebHookBuildTriggerType represents a trigger that launches builds on Bitbucket webhook invocations - ImageChange ImageChangeBuildTriggerType represents a trigger that launches builds on availability of a new version of an image - ConfigChange ConfigChangeBuildTriggerType will trigger a build on an initial build config creation WARNING: In the future the behavior will change to trigger a build on any config change |
2.1.40. .spec.triggers[].bitbucket
- Description
- WebHookTrigger is a trigger that gets invoked using a webhook type of post
- Type
-
object
Property | Type | Description |
---|---|---|
|
| allowEnv determines whether the webhook can set environment variables; can only be set to true for GenericWebHook. |
|
| secret used to validate requests. Deprecated: use SecretReference instead. |
|
| SecretLocalReference contains information that points to the local secret being used |
2.1.41. .spec.triggers[].bitbucket.secretReference
- Description
- SecretLocalReference contains information that points to the local secret being used
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| Name is the name of the resource in the same namespace being referenced |
2.1.42. .spec.triggers[].generic
- Description
- WebHookTrigger is a trigger that gets invoked using a webhook type of post
- Type
-
object
Property | Type | Description |
---|---|---|
|
| allowEnv determines whether the webhook can set environment variables; can only be set to true for GenericWebHook. |
|
| secret used to validate requests. Deprecated: use SecretReference instead. |
|
| SecretLocalReference contains information that points to the local secret being used |
2.1.43. .spec.triggers[].generic.secretReference
- Description
- SecretLocalReference contains information that points to the local secret being used
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| Name is the name of the resource in the same namespace being referenced |
2.1.44. .spec.triggers[].github
- Description
- WebHookTrigger is a trigger that gets invoked using a webhook type of post
- Type
-
object
Property | Type | Description |
---|---|---|
|
| allowEnv determines whether the webhook can set environment variables; can only be set to true for GenericWebHook. |
|
| secret used to validate requests. Deprecated: use SecretReference instead. |
|
| SecretLocalReference contains information that points to the local secret being used |
2.1.45. .spec.triggers[].github.secretReference
- Description
- SecretLocalReference contains information that points to the local secret being used
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| Name is the name of the resource in the same namespace being referenced |
2.1.46. .spec.triggers[].gitlab
- Description
- WebHookTrigger is a trigger that gets invoked using a webhook type of post
- Type
-
object
Property | Type | Description |
---|---|---|
|
| allowEnv determines whether the webhook can set environment variables; can only be set to true for GenericWebHook. |
|
| secret used to validate requests. Deprecated: use SecretReference instead. |
|
| SecretLocalReference contains information that points to the local secret being used |
2.1.47. .spec.triggers[].gitlab.secretReference
- Description
- SecretLocalReference contains information that points to the local secret being used
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| Name is the name of the resource in the same namespace being referenced |
2.1.48. .spec.triggers[].imageChange
- Description
- ImageChangeTrigger allows builds to be triggered when an ImageStream changes
- Type
-
object
Property | Type | Description |
---|---|---|
| from is a reference to an ImageStreamTag that will trigger a build when updated It is optional. If no From is specified, the From image from the build strategy will be used. Only one ImageChangeTrigger with an empty From reference is allowed in a build configuration. | |
|
| lastTriggeredImageID is used internally by the ImageChangeController to save last used image ID for build This field is deprecated and will be removed in a future release. Deprecated |
|
| paused is true if this trigger is temporarily disabled. Optional. |
2.1.49. .status
- Description
- BuildConfigStatus contains current state of the build config object.
- Type
-
object
- Required
-
lastVersion
-
Property | Type | Description |
---|---|---|
|
| ImageChangeTriggers captures the runtime state of any ImageChangeTrigger specified in the BuildConfigSpec, including the value reconciled by the OpenShift APIServer for the lastTriggeredImageID. There is a single entry in this array for each image change trigger in spec. Each trigger status references the ImageStreamTag that acts as the source of the trigger. |
|
| ImageChangeTriggerStatus tracks the latest resolved status of the associated ImageChangeTrigger policy specified in the BuildConfigSpec.Triggers struct. |
|
| lastVersion is used to inform about number of last triggered build. |
2.1.50. .status.imageChangeTriggers
- Description
- ImageChangeTriggers captures the runtime state of any ImageChangeTrigger specified in the BuildConfigSpec, including the value reconciled by the OpenShift APIServer for the lastTriggeredImageID. There is a single entry in this array for each image change trigger in spec. Each trigger status references the ImageStreamTag that acts as the source of the trigger.
- Type
-
array
2.1.51. .status.imageChangeTriggers[]
- Description
- ImageChangeTriggerStatus tracks the latest resolved status of the associated ImageChangeTrigger policy specified in the BuildConfigSpec.Triggers struct.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| ImageStreamTagReference references the ImageStreamTag in an image change trigger by namespace and name. |
| lastTriggerTime is the last time this particular ImageStreamTag triggered a Build to start. This field is only updated when this trigger specifically started a Build. | |
|
| lastTriggeredImageID represents the sha/id of the ImageStreamTag when a Build for this BuildConfig was started. The lastTriggeredImageID is updated each time a Build for this BuildConfig is started, even if this ImageStreamTag is not the reason the Build is started. |
2.1.52. .status.imageChangeTriggers[].from
- Description
- ImageStreamTagReference references the ImageStreamTag in an image change trigger by namespace and name.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is the name of the ImageStreamTag for an ImageChangeTrigger |
|
| namespace is the namespace where the ImageStreamTag for an ImageChangeTrigger is located |
2.2. API endpoints
The following API endpoints are available:
/apis/build.openshift.io/v1/buildconfigs
-
GET
: list or watch objects of kind BuildConfig
-
/apis/build.openshift.io/v1/watch/buildconfigs
-
GET
: watch individual changes to a list of BuildConfig. deprecated: use the 'watch' parameter with a list operation instead.
-
/apis/build.openshift.io/v1/namespaces/{namespace}/buildconfigs
-
DELETE
: delete collection of BuildConfig -
GET
: list or watch objects of kind BuildConfig -
POST
: create a BuildConfig
-
/apis/build.openshift.io/v1/watch/namespaces/{namespace}/buildconfigs
-
GET
: watch individual changes to a list of BuildConfig. deprecated: use the 'watch' parameter with a list operation instead.
-
/apis/build.openshift.io/v1/namespaces/{namespace}/buildconfigs/{name}
-
DELETE
: delete a BuildConfig -
GET
: read the specified BuildConfig -
PATCH
: partially update the specified BuildConfig -
PUT
: replace the specified BuildConfig
-
/apis/build.openshift.io/v1/watch/namespaces/{namespace}/buildconfigs/{name}
-
GET
: watch changes to an object of kind BuildConfig. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-
2.2.1. /apis/build.openshift.io/v1/buildconfigs
Parameter | Type | Description |
---|---|---|
|
| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server’s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. |
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| If 'true', then the output is pretty printed. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
|
| Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
- HTTP method
-
GET
- Description
- list or watch objects of kind BuildConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
2.2.2. /apis/build.openshift.io/v1/watch/buildconfigs
Parameter | Type | Description |
---|---|---|
|
| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server’s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. |
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| If 'true', then the output is pretty printed. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
|
| Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
- HTTP method
-
GET
- Description
- watch individual changes to a list of BuildConfig. deprecated: use the 'watch' parameter with a list operation instead.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
2.2.3. /apis/build.openshift.io/v1/namespaces/{namespace}/buildconfigs
Parameter | Type | Description |
---|---|---|
|
| object name and auth scope, such as for teams and projects |
Parameter | Type | Description |
---|---|---|
|
| If 'true', then the output is pretty printed. |
- HTTP method
-
DELETE
- Description
- delete collection of BuildConfig
Parameter | Type | Description |
---|---|---|
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both. |
|
| Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list or watch objects of kind BuildConfig
Parameter | Type | Description |
---|---|---|
|
| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server’s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. |
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
|
| Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a BuildConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
2.2.4. /apis/build.openshift.io/v1/watch/namespaces/{namespace}/buildconfigs
Parameter | Type | Description |
---|---|---|
|
| object name and auth scope, such as for teams and projects |
Parameter | Type | Description |
---|---|---|
|
| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server’s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. |
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| If 'true', then the output is pretty printed. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
|
| Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
- HTTP method
-
GET
- Description
- watch individual changes to a list of BuildConfig. deprecated: use the 'watch' parameter with a list operation instead.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
2.2.5. /apis/build.openshift.io/v1/namespaces/{namespace}/buildconfigs/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the BuildConfig |
|
| object name and auth scope, such as for teams and projects |
Parameter | Type | Description |
---|---|---|
|
| If 'true', then the output is pretty printed. |
- HTTP method
-
DELETE
- Description
- delete a BuildConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. |
|
| Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both. |
|
| Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified BuildConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified BuildConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the |
|
| Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified BuildConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
2.2.6. /apis/build.openshift.io/v1/watch/namespaces/{namespace}/buildconfigs/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the BuildConfig |
|
| object name and auth scope, such as for teams and projects |
Parameter | Type | Description |
---|---|---|
|
| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server’s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. |
|
| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. |
|
| A selector to restrict the list of returned objects by their fields. Defaults to everything. |
|
| A selector to restrict the list of returned objects by their labels. Defaults to everything. |
|
|
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
|
| If 'true', then the output is pretty printed. |
|
| resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset |
|
| Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. |
|
| Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
- HTTP method
-
GET
- Description
- watch changes to an object of kind BuildConfig. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |