My First Continuous Delivery Pipeline
Thursday, February 4, 2016
Build in red all weekend
Dashboard needs to support the Devs work
Ask them "what do you need to support your work"
99% of technology problems are people problems
Relationships and communication
No changes to code in the read that aren't fixing to broken build
Have metrics for the definition of "working" code and get rid of the rest
A/B testing w/ clear definition of success in each
Pipeline should be a collaborative definition --> build trust in the pipeline
How to organize team for CI/CD? N n
Code should go through as few env's as possible from laptop to prod
# of env's will depend on maturity, communications, etc., of teams
Created with Microsoft OneNote 2016.