Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CI servers: hosted, self-hosted or from scratch...

JP Boily
September 02, 2014

CI servers: hosted, self-hosted or from scratch (!!!)?

This talk is about all the options you have in terms of CI servers...and yes, I wills how you how to code your own (crappy) CIaaS! You should not do that ever by the way, pay for hosted!

JP Boily

September 02, 2014
Tweet

More Decks by JP Boily

Other Decks in Technology

Transcript

  1. Rainforest QA “We do QA as a service, making it

    simple and fast to test your webapp in multiple browsers. Backed by @ycombinator + @heavybit” rainforestqa.com
  2. Why hosted? Dead easy to setup and use It just

    works No maintenance Work on your product, not on CI!!!
  3. Common features • Support multiple languages, frameworks, DB, etc. •

    Support continuous deployment to multiple hosts • GitHub Pull Request integration
  4. Insanely fast, parallel building <3 Open Source too (new &

    limited) Build and deploy Docker containers Can SSH into build servers
  5. You should pay for a hosted CI, but if you

    don’t want… My 2 cents
  6. A lot of plugins By far, the most popular Jenkins

    Painful to have a nice setup IMHO Former Hudson, before Oracle screwed up
  7. Drone Super easy to setup “All” you need is “built-in”:

    GitHub, notifications, deployment… Builds run in Docker containers by drone.io
  8. Moar CI… Bamboo, self-hosted: by Atlasssian, tight integration with JIRA

    CruiseControl (.net, .rb) Strider CD, CI JOE (best name), and tons and tons more…
  9. Not the best option in most cases IMHO, but if

    you have high security requirements or really unusual setup that doesn't work on hosted, this is for you. My 2 cents