Chapter 10 ■ Deployment ConsiDerations■ Tip Git is a very popular option for source control, though it can be confusing for beginners. you can find a great
introductory, though very thorough, tutorial at https://www.atlassian.com/git/tutorials/.
One of the handy things about a good CI process is that it can be triggered when a developer places their changes
back into the remote code repository. Have a look at Figure 10-3.
Figure 10-3. A high level look at Continous Integration
At a very high level this diagram depicts a typical CI process. The developer has committed and pushed her code
changes to the version control system; now her changes are available to the rest of the team. Of particular note here is
that the act of pushing up these changes to the version control system has triggered a build of the code. The build can
be a very complicated affair and the CI process is often tailored to manage this complexity on your behalf. Figure 10-3
shows that after the code is successfully built we run tests; this is a crucial part of the whole process as it will prevent
broken software going into production. Another crucial aspect of the process is the reporting because developers and
other stakeholders need to be aware of what has occurred (this is often available as a report in the CI system and sent
to the team via email).