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)

Creating the views

Let's return to the web-shop project. If you have not yet added the required assets for debugging and resolved your dependencies, you should do this. Now, a little information on ASP.NET MVC. MVC is short for Model-View-Controller. Basically, we have a controller, which is sitting on our backend waiting for requests. Whenever a request is sent to the controller, it will serve up an HTML page, a so-called view. The controller typically passes a model, some C# class with properties and methods, to the view which the view can use to render information on the page. MVC is a common pattern used in many languages (it is certainly not C#- or .NET-specific).

In your file explorer, you can see that .NET already created a HomeController and Home view. MVC is convention-based, meaning that when you browse for a Home page, in this example http://mywebsite.com/Home...