AngularJS and Continuous integration (part 1)

Continuous integration for front-end code has become such an important part of my flow that I can’t think how teams survive without it.

In this blog series I’d like to share my journey building our AngularJS SPA and the challenges we faced incorporating CI.

Implementing CI for front-end apps has been a massive eye opener for me and really leveled-up our codebase quality. Some might argue: “Meh, it’s just javascript on the browser. Why waste time polishing a turd?”. Let me tell you, you need CI for your SPA just as much as your need it for your fancy Java Spring back-end.

It took me quite some time to get my current project to a point where we started to see the value that CI adds. In an environment where deployments are scheduled and tightly wound up with red tape, deploying quick fixes is not an option. You need to be so sure of the quality of the artifacts your team produces so that you can push that big red deploy button and go enjoy your weekend.

CI is much more that just plonking your code on git and triggering tests on changes. It’s about putting your team in the position to deploy high quality on the spot, receive instant feedback and react to evolving business requirements with the speed of light: It opens the gate to continuous delivery.

I’m looking forward to hearing what others have done so feel free to comment below or drop me a line @cmptrwizard