{"id":131,"date":"2016-06-15T12:46:13","date_gmt":"2016-06-15T12:46:13","guid":{"rendered":"http:\/\/redmonk.com\/fryan\/?p=131"},"modified":"2016-07-26T17:57:18","modified_gmt":"2016-07-26T17:57:18","slug":"ci-the-cloud-native-on-ramp-and-the-dominance-of-jenkins","status":"publish","type":"post","link":"https:\/\/redmonk.com\/fryan\/2016\/06\/15\/ci-the-cloud-native-on-ramp-and-the-dominance-of-jenkins\/","title":{"rendered":"CI: The Cloud Native On Ramp and The Dominance of Jenkins"},"content":{"rendered":"

TL; DR<\/strong> \u2013 If you are trying to modernise your development practices, or go cloud native, without CI\/CD you are doing it wrong<\/p>\n

Possibly the most frequent piece of advice I have given over the last number of years has been for development organisations to get a continuous integration (CI) system into place. It is closely followed by looking at your deployment pipeline, but without, at least, the CI building block there is pretty much nothing else a development organisation is going to do to become more productive that will have even moderate longer term success.<\/p>\n

When it comes to the world of cloud native having a CI\/CD pipeline in place is basic table stakes. This was very aptly summed up recently by Kelsey Hightower<\/a>\u00a0from\u00a0Google when he said:<\/p>\n

\n

If you don't have a CI system capable of building your application, then Kubernetes is the least of your problems. Focus on CI first.<\/p>\n

— Kelsey Hightower (@kelseyhightower) June 10, 2016<\/a><\/p><\/blockquote>\n