This document discusses how one company embraced continuous integration (CI) over time by: 1) Switching from basic version control and no automated testing to using Jenkins for CI with multiple language support across various environments. 2) Expanding their practices to include DevOps automation tools, testing approaches like TDD/BDD, and switching to Agile. 3) Encouraging changes within the company through technical talks, code reviews, and open source contributions to improve their work culture and practices.

1. How we embraced CI
Gavin Davies
Principal Software Developer, ___

3. TAKE HEART!

4. ● Single product company (mostly)
● Basic VCS
● No automated tests
● No enforced standards
● No release process
● No CI
... but still successful
Humble beginnings (circa 2007)

8. Switching to Jenkins (hudson)

9. Wall displays

10. Developing our own Jenkins plugins

11. Multiple language support
● Slaves for:
○ Various versions of PHP
○ Java/Clojure
○ .Net
○ Ruby
● Slave nodes are a mixture of:
○ "Metal"
○ Cloud-based (EC2, Rackspace)
○ Local VMs

12. "DevOps"
● Automation
● Puppet/Chef/Capistrano/Ansible etc
● Vagrant

13. Part of a wider story
● TDD/BDD
● Tech talks
● Hack nights
● Code reviews
● Switching to Agile
● Technical blogging
● Open source contribution
● From Accurev to SVN to Git
● Outside work
○ Unified Diff
○ Cardiff Dev Workshop

14. You can make changes
You CAN make changes in your workplace.
You CAN make it a better place to work,
technically and culturally.
Never sit back and moan. Do something about
it!
Start small. Start simple.

15. How can I do this?
● One thing at a time
● Make a good case
● Don't be rude or condescending
● Don't give up easily!