February 04 - 21:00
This is part 1 of (atleast 3, hopefully 4) in a series of posts I'm going to be writing up on using the DotCI plugin with JenkinsCI. I realized while writing up another post (it'll be part 3 of this series) that this should be a series of posts or it's going to turn in to a very long rant looking wall of text.
I'm looking at creating a lot of builds for one of our sections in the product as we're in the process of moving into a more microservice oriented infrastructure, it means splitting some things up into smaller packages that does one thing well.
I've used TravisCI for open source projects at Falcon and my own projects all run tests with Travis, it's a great product, and the ease of use and setup it brings with it is pretty much unrivaled when comparing Travis to Jenkins. Naturally, I would love to see Jenkins being able to make builds on the fly, like Travis.
DotCI is a project made by Groupon, it aims to make it really easy to test your code and push the result of the build to a GitHub commit so you can see the build status on the commit.
Of course you can achieve all these things with some manual work, but no one likes manual work, that's why we're in the automation business!
DotCI does a lot of interesting things, it requires a GitHub application to get a list of all your repos (it'll fetch your own and your organizations repos). Once you're authorized you can then select a repo from the dropdown list and create a build, doing that will enable a custom webhook on GitHub used for pushes and opening PR's.
Stay tuned for part 2 - Getting JenkinsCI ready for the DotCI plugin