-
Notifications
You must be signed in to change notification settings - Fork 249
Version History and Changes
Andrew Bayer edited this page Dec 13, 2016
·
14 revisions
The plugin page on the Jenkins project wiki always will contain a full list of changes in releases of the Declarative Pipelines plugin, but you can find more detail on specific changes here.
- Release Date: December 13, 2016
-
Major Changes:
-
COMPATIBILITY BREAKING SYNTAX CHANGE: The
jobProperties
section has been renamed toproperties
. - New Jenkins CLI command for validating/linting Declarative
Jenkinsfile
s.
-
COMPATIBILITY BREAKING SYNTAX CHANGE: The
- Release Date: November 17, 2016
-
Major Changes:
-
COMPATIBILITY BREAKING SYNTAX CHANGE: The
notifications
section has been removed, and thepostBuild
section has been renamed topost
, for consistency with post-stage actions. Usepost
for what you had been using bothpostBuild
andnotifications
. - New
dockerfile
option foragent
to auto-build a Dockerfile (defaults toROOT_DIR/Dockerfile
ifdockerfile:true
is used, otherwise uses value ofdockerfile
) and run the build in a container based on that image. - New
when
section for an individualstage
. Takes a block of arbitrary Pipeline code, runs it, and only executes thestage
's contents if that code block returnstrue
.
-
COMPATIBILITY BREAKING SYNTAX CHANGE: The
- Release Date: November 2, 2016
-
Major Changes:
-
COMPATIBILITY BREAKING SYNTAX CHANGE: Steps inside a
stage
now need to be in asteps
block. This was needed to support per-stage
configuration of a number of sections, as described below. - New
post
section supported inside astage
for post-stage
actions. This behaves the same as thepostBuild
section, but runs after a singlestage
. - New
agent
section supported inside astage
. This overrides the top-levelagent
configuration for the individualstage
. - New
tools
section supported inside astage
. This allows scopingtools
on a per-stage
basis. - New
environment
section supported inside astage
. This allows scopingenvironment
on a per-stage
basis. - A new configuration option, available both in the Jenkins global configuration and in folder configurations (such as GitHub Multibranch Pipelines), for specifying a default label to use for Docker agents.
- New
wrappers
section at the top-level, for wrapping the entire build in a block-scoped step, such asretry
ortimeout
.
-
COMPATIBILITY BREAKING SYNTAX CHANGE: Steps inside a
- Release Date: October 11, 2016
-
Major Changes:
- New
triggers
,jobProperties
andparameters
sections at the top-level. - New syntax for specifying to run on any node -
agent any
- Allow function or step calls in the values of environment variables in the
environment
section.
- New
Documentation
- Getting Started
- Running multiple steps
- Controlling your build environment
- Environment variables
- Reporting test results and storing artifacts
- Notifications
- Deployment and credentials
- Parallelism
- Triggering runs
- Parametrized pipelines
- Pipeline options and log rotation
- Jenkinsfile validation from the CLI
- Advanced pipeline authoring
- Syntax reference
- Version history and changes
Examples