Skip to content
This repository was archived by the owner on Nov 5, 2024. It is now read-only.

Commit 325c879

Browse files
committed
line breaks
1 parent e534879 commit 325c879

File tree

1 file changed

+34
-34
lines changed

1 file changed

+34
-34
lines changed

docs/modules/ROOT/pages/glossary/index.adoc

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -2,104 +2,104 @@
22
:icons: font
33
:source-highlighter: highlightjs
44

5-
**{ProductName}**
5+
**{ProductName}** +
66
A platform to automate the process of building, testing, and deploying applications to the hybrid cloud. {ProductName} offers enterprise-grade security and customizable feature sets.
77

8-
**build pipeline customization**
8+
**build pipeline customization** +
99
The ability to update and manage build pipelines for each component in an application.
1010

11-
**cluster**
11+
**cluster** +
1212
A Kubernetes deployment with nodes that run containerized applications and a control plane that manages the nodes.
1313

14-
**commit**
14+
**commit** +
1515
A change to one or more files. In {ProductName}, commits that you make to a linked Git repository move through the pipeline and automatically get published.
1616

17-
**component**
17+
**component** +
1818
An image that {ProductName} builds from source code in a repository. One or more components that run together form an application.
1919

20-
**Conftest**
20+
**Conftest** +
2121
A utility for testing structured configuration data. Use Conftest to validate container information.
2222

23-
**enterprise contract (EC)**
23+
**enterprise contract (EC)** +
2424
A set of release policies that you apply to your managed environment. Use the EC to prevent releases that are not compliant with Supply-chain Levels for Software Artifacts (SLSA) guidelines.
2525

26-
**ephemeral environment**
26+
**ephemeral environment** +
2727
A temporary environment that executes each integration scenario. The system creates ephemeral environments dynamically on demand, and then removes them after it completes the build pipeline.
2828

29-
**integration test**
29+
**integration test** +
3030
A pipeline that you set up in GitHub. When you add components, it tests each one individually, and then tests the application as a whole.
3131

32-
**IntegrationTestScenario**
32+
**IntegrationTestScenario** +
3333
A parameter that the integration service uses to test application components.
3434

35-
**Java build service**
35+
**Java build service** +
3636
A group of utilities that accelerates build times, locates dependencies in final images, and meets product security requirements by managing the construction of Java dependencies.
3737

38-
**lifecycle run**
38+
**lifecycle run** +
3939
The processes that automatically occur after a merge or pull request is resolved. These processes can include build tests, integration tests, and TaskRuns.
4040

41-
**managed environment**
41+
**managed environment** +
4242
An application release target. A separate managed environment team, such as an Site Reliability Engineering (SRE) team, manages the environment. The environment is in an external workspace.
4343

44-
**managed workspace**
44+
**managed workspace** +
4545
A workspace that mirrors some details of an already existing workspace. Supporting teams can create a managed workspace to grant limited permissions to development teams in the production environment.
4646

47-
**OSBS features**
47+
**OSBS features** +
4848
The layered image build service, or OSBS (derived from OpenShift Build Service), is a tool for building layered images. With OSBS features, you can build base RHEL images, layered images, and the builder image itself.
4949

50-
**persister**
50+
**persister** +
5151
A component that moves all of the relevant PipelineRun information, known as the Pipeline output, to an external storage that is outside of the cluster’s etcd database. The persister runs after the system completes the PipelineRun.
5252

53-
**pipelines as code**
53+
**pipelines as code** +
5454
A practice that defines pipelines by using source code in Git. Pipelines as Code is also the name of link:https://pipelinesascode.com[a subsystem] that executes those pipelines.
5555

56-
**pipeline results**
56+
**pipeline results** +
5757
Systems that retain the history and details of builds.
5858

59-
**PipelineRun**
59+
**PipelineRun** +
6060
A collection of TaskRuns that are arranged in a specific order of execution. A valid pipeline is compliant with the customer’s enterprise contract.
6161

62-
**pipeline service**
62+
**pipeline service** +
6363
A managed service that securely runs Tekton pipelines. It also stores the metadata and pipeline logs that are related to an executed pipeline in a separate database.
6464

65-
**product security test**
65+
**product security test** +
6666
A test that assesses the security of build inputs and outputs with vulnerability scanning, code scanning, image testing, and result reporting. It also identifies outdated images, applications, and build pipelines.
6767

68-
**pruner**
68+
**pruner** +
6969
A component that removes resources that are associated with the completed PipelineRuns. The system assigns resources, such as pods, to every PipelineRun. Without a pruner, these resources remain in the cluster indefinitely, even after the system completes the PipelineRun.
7070

71-
**release pipeline**
71+
**release pipeline** +
7272
A pipeline that defines the process for validating snapshots against the enterprise contract. They also provide an array of release destinations other than GitOps deployments.
7373

74-
**security testing**
74+
**security testing** +
7575
A process that determines if images meet security quality standards.
7676

77-
**signature and provenance**
77+
**signature and provenance** +
7878
Mechanisms that use Tekton chains to extract and store the metadata of the PipelineRuns, sign that metadata, and then store it in the image registry that is next to the component image.
7979

80-
**snapshot**
80+
**snapshot** +
8181
A set of component and container images that specifies which components the system should deploy with which container images. The system creates a snapshot when it finishes running a component's build pipeline.
8282

83-
**static environment**
83+
**static environment** +
8484
A set of compute resources that you can use to develop, test, and stage your applications before you release them. You can share static environments in all applications in the workspace.
8585

86-
**Supply-chain Levels for Software Artifacts (SLSA)**
86+
**Supply-chain Levels for Software Artifacts (SLSA)** +
8787
A link:https://slsa.dev/[security framework] that helps prevent tampering by securing the packages and infrastructure of customers’ projects.
8888

89-
**task**
89+
**task** +
9090
One or more steps that run container images. Each container image performs a piece of construction work.
9191

92-
**TaskRun**
92+
**TaskRun** +
9393
A process that executes a task on a cluster with inputs, outputs, and execution parameters. The system creates a TaskRun on its own, or as a part of a PipelineRun for each task in a pipeline.
9494

95-
**Tekton**
95+
**Tekton** +
9696
A Knative-based framework for CI/CD pipelines. Tekton is decoupled which means that you can use one pipeline to deploy to any Kubernetes cluster in multiple hybrid cloud providers. Tekton stores everything that is related to a pipeline in the cluster.
9797

98-
**Tekton chains**
98+
**Tekton chains** +
9999
A mechanism to secure the software supply chain by recording events in a user-defined pipeline.
100100

101-
**Tekton integration testing**
101+
**Tekton integration testing** +
102102
A process that uses Tekton tasks to support the setup and execution of dynamic application tests against container images.
103103

104-
**workspace**
104+
**workspace** +
105105
A storage volume that a task requires at runtime to receive input or provide output.

0 commit comments

Comments
 (0)