Name: intro-to-declarative-pipeline
Owner: CloudBees
Description: A gentle introduction to developing Declarative Pipelines for Jenkins.
Created: 2018-03-03 12:38:28.0
Updated: 2018-05-24 13:34:30.0
Pushed: 2018-05-16 16:07:51.0
Size: 6695
Language: null
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
This repository contains the instructions and learning materials associated with a hands on training workshop called Introduction to Declarative Pipelines that is designed to teach the following key concepts:
A PDF version of the presentation that accompanies this workshop can be found here: Introduction%20to%20Declarative%20Pipeline%20-%20Hands%20On.pdf
The exercises covered in the workshop are available at the following links:
Important Note: The training content contained in this workshop is kept up to date with the latest releases of pipeline plugins and not all features will be available in Jenkins environments that are not updated regulary or within CAP (the CloudBees Assurance Program). The following are the currently required Pipeline plugin versions:
In order to follow along with the hands on portion of the workshop students should have the following resources available to them:
Detailed set-up instructions are available at Setup
See: Releases
The content in this repository (with the important exception of the PDF, see note below) is Open Source material released under the Apache 2.0 License. Please see the LICENSE file for full license details.
Important Note: The `Introduction to Declarative Pipeline - Hands On.pdf
` file contains corporate identify materials that are proprietary to CloudBees, Inc. that cannot be reused without written permission from CloudBees, Inc.
Although the code in this repository was originally created by employees of CloudBees, Inc. to use in training customers your use of this material is not sponsored or supported by CloudBees, Inc.
If you have any questions, feedback, suggestions, etc. please submit them via issues or, even better, submit a Pull Request!