- [Instructor] Welcome back! In this lecture, we'll provide you with an understanding of the basic principles of Jenkins Pipelines and how to use them to automate your own CICD workflows.

Okay, let's begin. When it comes to building, releasing, and updating software applications frequently and reliably, you need to lean heavily on automated processes. Automation in the form of CICD is the goal that you should strive for. CICD is used to model all part of your integration workflow. For example, build, test, package, and deploy stages should be configured within your pipeline. With your CICD pipeline configured and enabled, then as each developer completes the feature development, and commits them to the main integration branch, the CICD pipeline should be triggered to perform each of the individual integration stages.

Jenkins provides great support for modeling and configuring CICD pipelines. Some benefits attributed to using Jenkins pipelines are speed, Jenkins CICD pipelines, by their very nature, are automated, and all of the execution stages can be performed completely hands-off. Productivity, developers can maintain their focus on building new product features, rather than performing manual testing and release procedures. Reduced risk, with automated test suites in place, the product can continually regression testing to ensure that it remain bug free. Time to market, features are released far quicker into production and therefore into the hands of customers. Security, the codebase and application can be rigorously security tested repeatedly to ensure that the application, once released into production, is battle hardened.

Now that we understand the benefits associated with using pipelines, let's move on and explore how Jenkins provides two different syntaxes for creating and configuring pipelines, which cover both ends of the pipeline complexity spectrum.

Okay, go ahead and close this lecture and we'll see you shortly in the next one.