CI/CD and Open Source Projects

Transcript

1. CI/CD and Open Source Projects Dimitry Ushakov (dimitry.ushakov@rackspace.com) Melissa Kam (melissa.kam@rackspace.com)
3. • • •
4. • • • • •
5. Upstream code Downstream code Combined code Unit tests Func tests Sonar Qube Perf tests Perf tests Perf tests
10. Patch #1 of "Adding user log messages in deployer" submitted by devdatta-kulkarni failed Arbor merging or testing. See #298 of gerrit-patch-trigger for details. http://ci.rs-paas.com/job/gerrit-patch-trigger/298/console https://review.openstack.org/172413
15. • Continuous for lower environments • Single push for staging & production • Allows for Product/Engineering input on features
16. staging-api.rackspace.com
17. staging-api.rackspace.com b-staging-api.rackspace.com
18. staging-api.rackspace.com b-staging-api.rackspace.com Functional Tests
19. staging-api.rackspace.com b-staging-api.rackspace.com
20. staging-api.rackspace.com b-staging-api.rackspace.com Functional Tests
21. staging-api.rackspace.com
22. • WHY: Developers need a quick environment • latest snapshot • specific branch • specific release • REQUIREMENT: Specific to developer and ephemeral • Customizable deployment • Environment mimics production • Developers can muck it up, delete it, and recreate it in minutes • SOLUTION: • Jenkins + Ansible + Chef FTW!
23. • Pingdom only works so well • Necessary until we get all infrastructure monitoring in place • Runs functional tests in staging/production and reports failures by email to dev list
24. • Developers are your friends! • Ops are your BEST friends! • Use data/tests for gate keeping • prevent the release of an artifact if tests fail • build in coverage/quality gates • Know the guts of the system • Builds team confidence • Knowledge of how to break the system