Skip to content

Commit 4e7db29

Browse files
authored
Merge pull request #13544 from bmcelvee/build-overview-followup
Edits to understanding builds
2 parents b423732 + b5ce8ff commit 4e7db29

File tree

4 files changed

+14
-14
lines changed

4 files changed

+14
-14
lines changed

_topic_map.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Name: Builds
3333
Dir: builds
3434
Distros: openshift-*
3535
Topics:
36-
- Name: How builds work
36+
- Name: Understanding builds
3737
File: understanding-builds
3838
- Name: Creating build inputs
3939
File: creating-build-inputs

builds/understanding-builds.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[id='understanding-build']
2-
= How builds work
2+
= Understanding builds
33
include::modules/common-attributes.adoc[]
44
:context: understanding-builds
55
toc::[]

modules/builds-about.adoc

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,12 @@
22
// * assembly/builds
33

44
[id='builds-about-{context}']
5-
= What is a build?
5+
= Builds
66

77
A _build_ is the process of transforming input parameters into a resulting
88
object (build object). Most often, the process is used to transform input
99
parameters or source code into a runnable container image.
1010

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-
1511
{product-title} uses Kubernetes by creating containers
1612
from build images and pushing them to a container image registry.
1713

@@ -50,10 +46,10 @@ specified.
5046
Additionally, the Pipeline build strategy can be used to implement sophisticated
5147
workflows including continuous integration and continuous deployment.
5248

53-
.Additional resources
49+
//.Additional resources
5450

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].

modules/builds-buildconfig.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,17 @@
22
// * assembly/builds
33

44
[id='builds-buildconfig-{context}']
5-
= What is a BuildConfig?
5+
= BuildConfigs
66

77
A build configuration describes a single build definition and a set of
88
triggers for when a new build is created. Build configurations are defined
99
by a `BuildConfig`, which is a REST object that can be used in a POST to the API
1010
server to create a new instance.
1111

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+
1216
Depending on how you choose to create your application using {product-title}, a
1317
`BuildConfig` is typically generated automatically for you if you use the web
1418
console or CLI, and it can be edited at any time. Understanding the parts that

0 commit comments

Comments
 (0)