gistfile1.txt

goal: how to build an awesome CI for your organization.  

Couple of years ago I was webdeveloper at Groupon working on a monlithic RoR webapp. 
We had grown rapidly and the webapp saw incredible amount of work put in. This also bought in lots of cucumber  tests and our build time shot up to 40 mintues. 

My Name is Surya Gaddipati, This is my story of my epic journey to build an awesome CI at groupon. 

CI is often setup as afterthought 
  > Teams consider it unimportant in grand scale of things
  > Teams often don't have the experience, interest 
  > Bad CI expereince always has a strong effect on team's morale, I've seen devs quit their job at other places I've worked
  > Slow, flaky CI is worse than having no CI. Don't do it. 
  > Bad tools -> Bad culture -> Bad tools. Vicious cycle.
  
Point of this talk
 > I hoping to present my experice building CI system that is a joy to use at groupon.
 > Hopefully discuss some of the  tools are outthere to help you build a good CI experience
 
 Tools 
  > Jenkins 
    > 1000's of plugins 
    > Popular/Familiar 
    > Easy to setup get going. Supported on wide range of platforms.
    > Many reasons for not choosing travisci/circleci/codeship
  > Github 
  
  CI Challenges microservices
   > Clean execution environments
   > Github flow integration
   > Github integration
   > Easy job/creation 
   > Authorization github
   > Private repo support via deploy keys. 
   > Easy paralliztion
   > Version controlled job configs 
   >Beautiful/Sensible UI.
   > Access to metrics 
   > Extensible for specail cases.
 

    DotCi Plugin for jenkins