Pipeline Syntax. Differences when considering top and phase level Agents

This area develops regarding the information introduced in Getting started with Pipeline and really should be addressed entirely as being a guide. To learn more about how exactly to make use of Pipeline syntax in practical examples, relate to the Using a Jenkinsfile portion of this chapter. At the time of variation 2.5 for the Pipeline plugin, Pipeline supports two discrete syntaxes that are detailed below. When it comes to advantages and disadvantages of each, understand Syntax Comparison.

As talked about in the beginning of this chapter, the essential fundamental part of a Pipeline could be the “step”. Essentially, actions tell Jenkins how to handle it and act as the building that is basic both for Declarative and Scripted Pipeline syntax.

For a summary of available actions, please relate to the Pipeline procedures guide containing a comprehensive variety of actions included in Pipeline along with actions given by plugins.

Declarative Pipeline

Declarative Pipeline is really a reasonably new addition to Jenkins Pipeline [1] which presents an even more simplified and opinionated syntax along with the Pipeline sub-systems.

All valid pipelines that are declarative be enclosed within a pipeline block, as an example:

The fundamental statements and expressions that are legitimate in Declarative Pipeline proceed with the exact exact exact same guidelines as Groovy’s syntax with all the exceptions that are following