In all chapters thus far, we have focused on a single tool to get the job done. Although I tried to select the most established and mature PHP-centric tools, at times it simply came down to preference or perspective. The case in this chapter is even more complicated than that.
Continuous integration can be done on any machine, including a developer's workstation. If you can spare the resources in terms of memory, disk space, and CPU cycles, you can make the CI process the responsibility of an existing machine, perhaps a file server or even your version control system. Another factor in making this decision is the size of the team. If you are the primary observer of the CI output, it might be convenient to have the automated builds performed on your machine. However, if your team size were slightly larger, it would be important to have the CI server centrally accessible. Carrying it around on your laptop might benefit yourself...