2 Introduction to Continuous Integration

 

This chapter covers

  • Create a central code repository as the starting point for our pipeline
  • Use the Toyota Production System as a model for software development
  • Reduce variation and bugs by using trunk based development process
  • Break down tasks into smaller chunks to be easily completed and reduce work in progress
  • Increase team efficiency by standardizing work environments
  • Document processes for others for better knowledge sharing
  • Automate the steps needed to build your product by using a continuous integration system

The assembly line is often mistaken as an invention by Henry Ford. However, the concept of an assembly line goes back decades prior to Ford’s use of it on his famous Model T. Clothing, machines, bicycles, and boats were all applications of the concept of moving pieces between divided pieces of labor as far back as the Industrial Revolution. Automated tracks of materials would move around assembly or unit production.

Henry Ford didn’t even create the automated assembly line. What he is famous for is his application of the assembly line by creating core principles that efficiently delivered his product from start to finish.

His principles were simple:

  • Place the tools and people in the order of operation.
  • Optimize the flow for each station of work.
  • Automate the line moving the pieces.

2.1 Source Code as Raw Material

 
 
 

2.2 Creating a Uniform Work Environment

 
 

2.3 Implementing Trunk Based Development on Your Team

 
 

2.4 Using Common Build Tools

 
 

2.5 Continuous Integration Systems to Automate Tasks

 

2.6 Using the Toyota Production System as a Development Model

 

2.7 Using Documentation to Accelerate Development

 
 
 
 

2.8 Putting it all together

 
 

2.9 Summary

 
 
 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage
test yourself with a liveTest