Skip to content

Commit

Permalink
"Overview" => "Getting Started" which more accurately captures that s…
Browse files Browse the repository at this point in the history
…ection's purpose
  • Loading branch information
R. Tyler Croy committed Nov 22, 2016
1 parent 2e61520 commit 5a2760f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 34 deletions.
2 changes: 1 addition & 1 deletion content/doc/book/pipeline/chapter.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
sections:
- overview
- getting-started
- jenkinsfile
35 changes: 2 additions & 33 deletions content/doc/book/pipeline/getting-started.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,40 +6,9 @@ layout: section
:author:
:email: [email protected]
:sectanchors:
:toc: left
:toc:

= Overview

== Audience and Purpose

This document is intended for novice users of the Jenkins pipeline feature. The
document explains what a pipeline is, why that matters, and how to create the
different kinds of pipelines.

== Why Pipeline?

While standard Jenkins "freestyle" jobs support simple continuous integration by
allowing you to define sequential tasks in an application lifecycle, they do not
create a record of execution that persists through any planned or unplanned
restarts, enable one script to address all the steps in a complex workflow, or
confer the other advantages of pipelines.

In contrast to freestyle jobs, pipelines enable you to define the whole
application lifecycle. Pipeline functionality helps Jenkins to support
continuous delivery (CD). The Pipeline plugin was built with requirements for a
flexible, extensible, and script-based CD workflow capability in mind.

Accordingly, pipeline functionality is:

* Durable: Pipelines can survive both planned and unplanned restarts of your Jenkins master.
* Pausable: Pipelines can optionally stop and wait for human input or approval before completing the jobs for which they were built.
* Versatile: Pipelines support complex real-world CD requirements, including the ability to fork or join, loop, and work in parallel with each other.
* Extensible: The Pipeline plugin supports custom extensions to its DSL (domain scripting language) and multiple options for integration with other plugins.


The flowchart below is an example of one continuous delivery scenario enabled by the Pipeline plugin:

image::/images/pipeline/realworld-pipeline-flow.png[title="Pipeline Flow", 800]
= Getting Started

== Pipeline Defined

Expand Down

0 comments on commit 5a2760f

Please sign in to comment.