Merge pull request circleci#4031 from circleci/rosie/pipelines-benefits

rosieyohannan · web-flow · commit ca6c96d91c19 · 2019-12-20T20:53:08.000Z
update pipelines benefits
diff --git a/jekyll/_cci2/api-intro.md b/jekyll/_cci2/api-intro.md
@@ -50,16 +50,9 @@ The CircleCI API v2 enables users to be authenticated by simply sending your API
 
 ### Pipelines
 
-The CircleCI API v2 includes the use of pipelines to assist you in triggering workflows from the CircleCI API. By enabling pipelines, you can take advantage of specific API use cases such as:
+The CircleCI API v2 requires you to enable pipelines on your project. By enabling pipelines, you can also take advantage of the following:
 
-- Use Pipeline parameters to trigger [conditional workflows](https://circleci.com/docs/2.0/pipeline-variables/#conditional-workflows).
-- API v2 triggering works with v2.1 config, allowing use of reusable config elements, including orbs.
-- You can now enable auto-cancel, within **Advanced Settings**, to abort workflows when new builds are triggered on non-default branches.
-
-For more detailed information on pipelines and how you can use them in your workflows and jobs, please see the following guides: 
-* [Enabling and Transitioning to Pipelines](https://circleci.com/docs/2.0/build-processing/) guide.
-* [Viewing Pipelines in the UI](https://circleci.com/docs/2.0/pipelines/#overview)
-* [Pipeline Variables](https://circleci.com/docs/2.0/pipeline-variables/#section=configuration)
+{% include snippets/pipelines-benefits.adoc %}
 
 #### Triggering a Pipeline with Parameters Example
 
diff --git a/jekyll/_cci2/build-processing.md b/jekyll/_cci2/build-processing.md
@@ -21,12 +21,7 @@ Most projects will have Pipelines enabled by default. Verify the project pipelin
 
 The pipelines feature enables use of the new [API endpoint to trigger builds with workflows](https://circleci.com/docs/api/#trigger-a-new-build-by-project-preview) and the following use cases:
 
-- New API endpoint to trigger builds, including running all workflows in the build.
-- Jobs named `build` will be wrapped in a workflows stanza by the processor.
-- Projects for which auto-cancel is enabled in the Advanced Settings will have workflows on non-default branches cancelled when a newer build is triggered on that same branch.
-- Use of configuration version 2.1 or higher requires pipelines to be turned on.
-
-**Notes:** It is important to carefully consider the impact of enabling the auto-cancel feature, for example, if you have configured automated deployment jobs on non-default branches.
+{% include snippets/pipelines-benefits.adoc %}
 
 ## Troubleshooting
 
diff --git a/jekyll/_includes/snippets/pipelines-benefits.adoc b/jekyll/_includes/snippets/pipelines-benefits.adoc
@@ -0,0 +1,13 @@
+* Use pipeline parameters to trigger [conditional workflows]({{ site.baseurl }}/2.0/pipeline-variables/#conditional-workflows).
+* Access to `version 2.1` config, which provides:
+    * [Resuable config]({{ site.baseurl }}/2.0/reusing-config/) elements, including executors, commands and jobs.
+    * Packaged resuable config, known as [orbs](https://circleci.com/orbs/).
+    * Improved config validation error messages.
+- You can now enable auto-cancel, within **Advanced Settings**, to abort workflows when new builds are triggered on non-default branches.
+
+**Note**, it is important to carefully consider the impact of enabling the auto-cancel feature, for example, if you have configured automated deployment jobs on non-default branches.
+
+For more detailed information on pipelines and how you can use their properties in your workflows and jobs, please see the following guides: 
+* [Transitioning to Pipelines]({{ site.baseurl }}/2.0/build-processing/#transitioning-to-pipelines)
+* [Viewing Pipelines in the UI]({{ site.baseurl }}/2.0/pipelines/#overview)
+* [Pipeline Variables]({{ site.baseurl }}/2.0/pipeline-variables/)
