When more than one programmer is writing code in a project, it's possible that one person will make changes to the source code that will conflict with the changes that the second person is making. In the past, teams would often have a person dedicated to just building the code. This seems like a foreign concept today, thanks to Continuous Integration systems, such as ThoughtWorks's open source Go Continuous Delivery and JetBrains's TeamCity, and classic open source systems like Jenkins. Today, teams can easily access the benefits of Continuous Integration (CI)—a known, up-to-date, and controlled build environment that is distinct from the ones developers have so that a team can have confidence that the solution still works in other environments, getting past most "it works on my machine" problems. In this recipe, we'll show you how to get started with Continuous Integration on your project using JetBrains's popular TeamCity.
ServiceStack 4 Cookbook
ServiceStack 4 Cookbook
Overview of this book
Table of Contents (18 chapters)
ServiceStack 4 Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Configuration and Routing
Services and Data Transfer Objects
Testing and Logging
Object Relational Mapping (OrmLite)
HTML and Form Data
Filters and Validators
Security and Authentication
Working with Redis
Integrating with Other Technologies
Getting Started
Testing Locally
Index
Customer Reviews