Pipeline as Code describes a set of features that allow Jenkins users to define pipelined job processes with code, stored and versioned in a source ...
Pipeline provides an extensible set of tools for modeling simple-to-complex delivery pipelines "as code" via the Pipeline domain-specific language (DSL) syntax.
Missing: /url | Show results with:/url
... pipelines "as code" via the Pipeline DSL. This section describes how to get started with creating your Pipeline project in Jenkins and introduces you to ...
Jenkins Pipeline includes built-in documentation and the Snippet Generator which are key resources when developing Pipelines. They provide detailed help and ...
From the Jenkins home page (i.e. the Dashboard of Jenkins' classic UI), click the name of your Pipeline project/item. On the left, click Pipeline Syntax and ...
This section builds on the information introduced in Getting started with Pipeline and should be treated solely as a reference. For more information on how ...
The vars directory hosts script files that are exposed as a variable in Pipelines. The name of the file is the name of the variable in the Pipeline. So if you ...
This guide provides a small selection of best practices for pipelines and points out the most common mistakes. The goal is to point pipeline authors and ...
Missing: /url | Show results with:/url
The Jenkins Configuration as Code (JCasC) feature defines Jenkins configuration parameters in a human-readable YAML file that can be stored as source code.
Once your Pipeline has completed, whether it succeeds or fails, you can go to the side panel for the run in the classic UI and click on "Restart from Stage".
Missing: /url | Show results with:/url