Jenkins User Boot Camp Classroom Live Boston, MA July 07, 2021

Course Overview

As organizations increase the usage of Jenkins, scaling up to deal new issues will arise when additional masters are added to the environment. Business critical challenges are inevitable because each master will require separate maintenance, security, and upgrades to remain functional. This course will teach you how to use Jenkins for your solution, resulting in:

1. Full control of all masters from one central control

2. Accelerated automation, development, and delivery

3. Meaningful, measurable, quantifiable performance enhancements

Part 1: Foundations of CI/CD in enterprise environments

In order to create an efficient Jenkins environment, the stability of the source control system & the Continuous Integration infrastructure needs to be determined. The root of the CD pipeline starts with the foundation of your environment which is constantly affected by automation, integration, testing and quality assessment, and so on.

1. What is Jenkins, CI & CD, and how can Jenkins help my business?

2. Introduction to Jenkins and its use for CI best practices

3. Feature overview: open-source Jenkins

4. Example deployment approaches: Dedicated hardware, Docker, AWS

Part 2: Agile Refresher

Agile development is creating more effective enterprises, and adoption of its values is at an all-time high. The ability to manage changing priorities, increase project visibility, and accelerate product delivery are but a few of the many benefits that Agile development creates. Overall performance has high expectations in today's digital landscape, and the implementation of Agile principles keep teams prepared for new demands, technologies, and trends.

1. The Agile Manifesto

2. Success with Scaling Agile

3. Agile Management Tools

4. Implementation of common tools

Part 3: Getting started with Jenkins

Jenkins is at the nucleus of integration & delivery, thus the mastery of it is essential for agile development teams. Pre-deployment, deployment, and post-deployment functionality should be planned and considered before the code is committed.

1. Key components of Jenkins

2. Jobs in Jenkins

3. Projects in Jenkins

4. Builds in Jenkins

5. Views

6. Jenkins Templates and modular jobs

Part 4: Jenkins plugins

One of the reasons for Jenkins popularity is because it has literally hundreds of plugins that are customized to expand usage and capabilities within all solutions. These days, the right plugin can assist in fixing problems that you didn’t even know you had.

1. Pipeline (Mainly these plugins - Input Step, Basic Steps, Build Step, Job, Groovy

2. Docker Pipelines & Commons

3. Using parameters and credentials with plugins

4. Choice parameters

5. Conditional Build Steps

6. GitHub

7. NodeJS

8. Terraform

9. Amazon Web Services & EC2 Container Services plugins

10. Notifications

Part 5: Integrating Jenkins and version control

Jenkins has excellent support for various source code management systems like CVS, Subversion, Git, and more. Complicated jobs continue to need modification, as a natural condition of CI, therefore integration is often a new configuration.

1. A Git example

2. Jenkins and best SCM practices with Github

3. Using Jenkins for Optimizing and Measuring Code Quality Code

4. Code Coverage Metrics

5. Running and using Builds

Part 6: Parameterized Builds

Any given project will have the option make it’s build parameterized. This enables jobs to be executed with version numbers, server URLs, node names, and specified organizational
markers. 

1. Adding Parameters

2. Passing Parameter Values

3. Executing a Parameterized Build

4. Jenkins credentials

Part 7: Automating Deployments

Automation is one of the most important components necessary for a development team to be agile. Deployment automation is tricky to implement, and many people think they are doing it correctly when they are not.

1. Deploying code

   1. Servers, Clients, and Workstations

   2. Docker & AWS Containers

   3. Terraform

2. Integrating automated tests (e.g.: Cucumber tests and any other) in Builds and Deployment jobs with Pipeline

3. Include Jenkins integration with JFrog Artifactory (DJ use Artifactory for different use cases, including storing docker images and registries)

Part 8: Handling Build Failures

Recognizing known issues, dealing with problems efficiently, and preventing future errors is a must when it comes to continuous delivery. Pipelines have introduced much greater traceability of changes to the build process, so that build fails can be dealt with immediately.

1. Detecting the source of a build failure

2. Troubleshooting Jenkins Builds

3. Build failure Analyzer

4. Build log scanning

5. Git Timeouts

Part 9: Folders in Jenkins

1. Folders
2. Folders Plus

Part 10: Merging

1. Validated Merges
2. Using GitHub for validated merges
3. Pull-Request Builder for GitHub
4. Templates

Part 11: Running a CI/CD Pipeline through Jenkins

https://jenkins.io/doc/book/pipeline/syntax/
1. Pipeline development tools
2. Pipeline Plugin
3. Trigger a pipeline