2 Pipeline as Code with Jenkins
This chapter covers
- How “Pipeline as Code” works with Jenkins
- An overview of Jenkinsfile structure and syntax
- Introduction to Blue Ocean, the new Jenkins user experience
- The difference between declarative and scripted Jenkins pipelines
- Integration of GitFlow model within Jenkins projects
- Tips to be more productive and efficient while writing Jenkinsfile for complex CI/CD pipelines
There’s no doubt that cloud computing has had a major impact on how companies build, scale, and maintain technology products. The ability to click a few buttons to provision machines, databases, and other infrastructure has led to an increase in developer productivity we’ve never seen before.
While it was easy to spin up simple cloud architectures, mistakes can easily be made while provisioning complex ones. Human error will always be present, especially when you can launch cloud infrastructure by clicking the buttons on the cloud provider web console.
The only way to avoid these kinds of errors is through automation, and “Infrastructure as Code” is helping engineers automatically launch cloud environments quickly and without mistakes. The growth of DevOps and the adoption of its practices have led to more tooling that can implement the “Infrastructure as Code” paradigm to a larger degree.