File tree Expand file tree Collapse file tree 4 files changed +14
-14
lines changed Expand file tree Collapse file tree 4 files changed +14
-14
lines changed Original file line number Diff line number Diff line change @@ -33,7 +33,7 @@ Name: Builds
33
33
Dir : builds
34
34
Distros : openshift-*
35
35
Topics :
36
- - Name : How builds work
36
+ - Name : Understanding builds
37
37
File : understanding-builds
38
38
- Name : Creating build inputs
39
39
File : creating-build-inputs
Original file line number Diff line number Diff line change 1
1
[id='understanding-build']
2
- = How builds work
2
+ = Understanding builds
3
3
include::modules/common-attributes.adoc[]
4
4
:context: understanding-builds
5
5
toc::[]
Original file line number Diff line number Diff line change 2
2
// * assembly/builds
3
3
4
4
[id='builds-about-{context}']
5
- = What is a build?
5
+ = Builds
6
6
7
7
A _build_ is the process of transforming input parameters into a resulting
8
8
object (build object). Most often, the process is used to transform input
9
9
parameters or source code into a runnable container image.
10
10
11
- A _build configuration_, or `BuildConfig`, is characterized by a _build strategy_
12
- and one or more sources. The strategy determines the process, while
13
- the sources provide its input.
14
-
15
11
{product-title} uses Kubernetes by creating containers
16
12
from build images and pushing them to a container image registry.
17
13
@@ -50,10 +46,10 @@ specified.
50
46
Additionally, the Pipeline build strategy can be used to implement sophisticated
51
47
workflows including continuous integration and continuous deployment.
52
48
53
- .Additional resources
49
+ // .Additional resources
54
50
55
- * Container image registry.
56
- * List of build commands.
57
- * For more information on how {product-title} uses Docker for builds, see the
58
- link:https://github.com/openshift/origin/blob/master/docs/builds.md#how-it-works[upstream
59
- documentation].
51
+ // * Container image registry.
52
+ // * List of build commands.
53
+ // * For more information on how {product-title} uses Docker for builds, see the
54
+ // link:https://github.com/openshift/origin/blob/master/docs/builds.md#how-it-works[upstream
55
+ // documentation].
Original file line number Diff line number Diff line change 2
2
// * assembly/builds
3
3
4
4
[id='builds-buildconfig-{context}']
5
- = What is a BuildConfig?
5
+ = BuildConfigs
6
6
7
7
A build configuration describes a single build definition and a set of
8
8
triggers for when a new build is created. Build configurations are defined
9
9
by a `BuildConfig`, which is a REST object that can be used in a POST to the API
10
10
server to create a new instance.
11
11
12
+ A _build configuration_, or `BuildConfig`, is characterized by a _build strategy_
13
+ and one or more sources. The strategy determines the process, while
14
+ the sources provide its input.
15
+
12
16
Depending on how you choose to create your application using {product-title}, a
13
17
`BuildConfig` is typically generated automatically for you if you use the web
14
18
console or CLI, and it can be edited at any time. Understanding the parts that
You can’t perform that action at this time.
0 commit comments