mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
32 lines
993 B
Plaintext
32 lines
993 B
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * assembly/builds
|
|
|
|
[id="builds-setting-maximum-duration_{context}"]
|
|
= Setting maximum duration
|
|
|
|
When defining a `BuildConfig`, you can define its maximum duration by setting
|
|
the `completionDeadlineSeconds` field. It is specified in seconds and is not
|
|
set by default. When not set, there is no maximum duration enforced.
|
|
|
|
The maximum duration is counted from the time when a build pod gets scheduled in
|
|
the system, and defines how long it can be active, including the time needed to
|
|
pull the builder image. After reaching the specified timeout, the build is
|
|
terminated by {product-title}.
|
|
|
|
.Procedure
|
|
|
|
* To set maximum duration, specify `completionDeadlineSeconds` in your
|
|
`BuildConfig`. The following example shows the part of a `BuildConfig`
|
|
specifying `completionDeadlineSeconds` field for 30 minutes:
|
|
*
|
|
----
|
|
spec:
|
|
completionDeadlineSeconds: 1800
|
|
----
|
|
|
|
[NOTE]
|
|
====
|
|
This setting is not supported with the Pipeline Strategy option.
|
|
====
|