Book Image

DevOps for Web Development

By : Mitesh Soni
Book Image

DevOps for Web Development

By: Mitesh Soni

Overview of this book

The DevOps culture is growing at a massive rate, as many organizations are adopting it. However, implementing it for web applications is one of the biggest challenges experienced by many developers and admins, which this book will help you overcome using various tools, such as Chef, Docker, and Jenkins. On the basis of the functionality of these tools, the book is divided into three parts. The first part shows you how to use Jenkins 2.0 for Continuous Integration of a sample JEE application. The second part explains the Chef configuration management tool, and provides an overview of Docker containers, resource provisioning in cloud environments using Chef, and Configuration Management in a cloud environment. The third part explores Continuous Delivery and Continuous Deployment in AWS, Microsoft Azure, and Docker, all using Jenkins 2.0. This book combines the skills of both web application deployment and system configuration as each chapter contains one or more practical hands-on projects. You will be exposed to real-world project scenarios that are progressively presented from easy to complex solutions. We will teach you concepts such as hosting web applications, configuring a runtime environment, monitoring and hosting on various cloud platforms, and managing them. This book will show you how to essentially host and manage web applications along with Continuous Integration, Cloud Computing, Configuration Management, Continuous Monitoring, Continuous Delivery, and Deployment.
Table of Contents (16 chapters)
DevOps for Web Development
About the Author
About the Reviewer

Configuring build job

Now that Git authentication is done with, let's configure a PetClinic build job:

  1. Click on the PetClinic build job on the Jenkins dashboard. Then, click on the Configure link. You'll see the following page as shown here:

  2. Under Source Code Management, provide the GitHub URL for the sample Spring project we forked earlier, as shown in the following screenshot:

  3. We will configure Build Triggers and the Build Environment as shown here:

  4. Under Build, click on Add build step and select Invoke top-level Maven targets. Select the Maven Version we configured in Global Tools Configuration. Enter the Maven target and click on Save:

  5. Let's manually trigger the build by clicking on Build Now. After the build is complete, you'll see this:

  6. Click on the build number, the one with the #  symbol. Open Console Output. Verify the Git operations executing before Maven target execution:

  7. Once source code is available in the build job's workspace, the Maven target will be executed and the...