We’ve been lax in implementing CI in the latest project I’m working on. Now that decision has caught up with me and its time to implement something. I mainly held off on CI because I couldn’t bring myself to have to setup another Jenkins instance. I’m a long time user and fan of Jenkins, I even developed the Perforce plugin for it back when it was called Hudson.
But these days, I no longer want to manage servers, be they physical or virtual. Life is just too short. Instead, I’d like to use one of the new CI services that has cropped up in recent years. For something as important as CI, I’m not going to make a blind choice. Especially, when we’ve been spoiled with how customizable Jenkins is. So let’s get down to reviewing some build tools…
Bootstrap 4 is moving from LESS to Sass!
In the early days of bootstrap, we had to rely on outside developers maintaining a port of bootstrap in Sass so that we could integrate with our existing Sass projects. It got better with Bootstrap 2 and an official Sass repo. But it always felt an after thought and you would get some strange problems every once in awhile as the main developers were lax in focusing on the Sass side of things.