Why You Should Have a Personal CI Server
As a developer, I rely on a CI server to take care of the day-to-day routine of building, testing and deploying software...so much so that I often find myself committing code after every new class or group of methods as a “fire and forget” signal to the CI server to go ahead and run my tests, check my code for style violations, and push a new version to the dev server. When I have finished my train of thought, I can jump into the CI server and either be greeted with a green tick or have a handy (and more importantly authoritative) list of issues to be addressed.
However, for all the convenience that a central CI server brings, there are times when this environment lets me down. Maybe my jobs are at the end of the queue, I can’t deploy to the dev servers during a certain time frame, or the configuration of the build just doesn’t quite do what I want it to do but I don’t have the authority to change it.
This got me thinking: why don’t I have my own personal CI server?
