In this chapter, we presented continuous integration practices and explored how Docker helps to implement them. We also looked at how to design a pipeline that ensures that our code always follows high standards and detects deviations as soon as possible. Using Git branches and pull requests in GitHub plays along with this, as we can determine when the code is ready to be merged into the main branch and deployed.
We then introduced Travis CI as a great tool to work with alongside GitHub to achieve continuous integration, and discussed its features. We learned how to create a pipeline in Travis CI, from the creation of the .travis.yml file, how to configure jobs, how to make the build push a validated Docker image to our Docker registry, and how to be notified.
We described how to speed up running sections in parallel, as well as how to set values as secrets. We also configured...
