This repository has been archived by the owner on Jul 22, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
Continuous Integration Best Practices
Benjamin Oakes edited this page Nov 18, 2013
·
2 revisions
Speakers: @leozh, @jdotp
Their definition: "auto deploy to mainline branch"
-
Want too make testing realistic
-
Programmable means automation
-
bootstrapping via AMI or dynamic config
-
awsofa.info
-
cloudinit in amz Linux and Ubuntu
-
creds not in puppet, should use private buckets
-
always use auto scaling groups for self healing
-
puppet runstages
-
rpm/deb in s3 instead of puppetmaster
-
puppet masters, at least 2
-
webmaker
-
openbadges
-
SOA
-
12 factor app
-
more deploys
-
visible ops, feedback loop
-
deploy by Jenkins
-
deploy via Debian package
-
cloudformation for drupal, etc
-
cloudformation used in deployment for fresh arch
-
NASA case study
-
same week as Olympics
-
built their own CDN
-
cloudformation template
-
cloudtest
- feature toggles
- does it work well in production?
A crowd-sourced conference wiki!
Working together is better. :)
- Speakers, for example:
- Recent Conferences
- Software
- Offline Access
- Contributors (More than 50!)
- Code Frequency