Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jm'Continuous Deployment: The Dirty Details'2015-04-22T10:08:00+00:00
http://www.slideshare.net/mikebrittain/mbrittain-continuous-deploymentalm3public
jmcd deploy etsy slides migrations database schema ops ci version-control feature-flagshttps://pinboard.in/https://pinboard.in/u:jm/b:7b09e64e7d8f/Consul case study from Hootsuite2014-11-27T16:05:57+00:00
http://code.hootsuite.com/distributed-configuration-management-and-dark-launching-using-consul/
jmconsul dark-launches feature-flags configuration distributed hootsuite notificationhttps://pinboard.in/https://pinboard.in/u:jm/b:f5817ff0c226/Netflix release new code to production before completing tests2014-10-10T21:15:54+00:00
http://techblog.netflix.com/2013/11/preparing-netflix-api-for-deployment.html
jmIf a build has made it [past the 'integration test' phase], it is ready to be deployed to one or more internal environments for user-acceptance testing. Users could be UI developers implementing a new feature using the API, UI Testers performing end-to-end testing or automated UI regression tests. As far as possible, we strive to not have user-acceptance tests be a gating factor for our deployments. We do this by wrapping functionality in Feature Flags so that it is turned off in Production while testing is happening in other environments.
]]>devops deployment feature-flags release testing integration-tests uat qa production ops gating netflixhttps://pinboard.in/https://pinboard.in/u:jm/b:2a3b3c58309f/