Book Image

Continuous Integration, Delivery, and Deployment

By : Sander Rossel
Book Image

Continuous Integration, Delivery, and Deployment

By: Sander Rossel

Overview of this book

The challenge faced by many teams while implementing Continuous Deployment is that it requires the use of many tools and processes that all work together. Learning and implementing all these tools (correctly) takes a lot of time and effort, leading people to wonder whether it's really worth it. This book sets up a project to show you the different steps, processes, and tools in Continuous Deployment and the actual problems they solve. We start by introducing Continuous Integration (CI), deployment, and delivery as well as providing an overview of the tools used in CI. You'll then create a web app and see how Git can be used in a CI environment. Moving on, you'll explore unit testing using Jasmine and browser testing using Karma and Selenium for your app. You'll also find out how to automate tasks using Gulp and Jenkins. Next, you'll get acquainted with database integration for different platforms, such as MongoDB and PostgreSQL. Finally, you'll set up different Jenkins jobs to integrate with Node.js and C# projects, and Jenkins pipelines to make branching easier. By the end of the book, you'll have implemented Continuous Delivery and deployment from scratch.
Table of Contents (15 chapters)

Testing a Web API

At this point, you are probably hoping we are getting to the delivery and deployment part, right? Almost, so hang on. There is just one more thing I would like to discuss, which is Web API testing. There are plenty of application types, such as desktop applications, embedded applications, and web applications like we created in this book. And, of course, all those applications can be created using a ton of languages and at least a gazillion frameworks. All of them take a different approach to testing and have their own testing frameworks. Throughout this book, we have used Jasmine, xUnit, and Selenium, to name but a few. In this day and age, companies want web services, though, be they JSON services or XML/SOAP services. And there is one thing I really like about those kinds of applications; they all operate on HTTP, no matter their underlying language or framework...