2 Introducing continuous integration

 

This chapter covers

  • Documenting requirements in your source code
  • Establishing a central code repository as the starting point for your pipeline
  • Automating the steps needed to build your product by using a continuous integration system
  • Creating a basic application to start development

It’s Monday, and you’ve been drinking your morning coffee and scrolling through emails when you see an invitation to a meeting titled “Kickoff.” You check the time and realize you are going to be late. Grabbing your laptop, you run to the conference room and see just one person sitting there, a product manager. As you close the door and walk to a seat, they say, “Glad you could make it; sorry about the last-minute invite, but we need to get something built this week. Our company would like to explore creating a new hello translation service that is cheaper and faster than our legacy system. In the future, we want to expand beyond just translating ‘hello,’ but our system will not scale. The conversation has been going on too long at this point, and I want to prove to them we can get something done quickly and still meet their targets. Do you think we can do it?”

A new service to replicate the functionality of an old service in less than a week, with better performance and at a cheaper cost? Sure, why not? What do you have to lose?

2.1 Where to start?

2.2 A greenfield project

2.3 The assembly line

2.4 Warehouses

2.5 Material

Summary