I recently was put on a project where we were doing development for a website. There was already a large code base, and we went in to add features in order to complete the site; including performing code refactoring when necessary. In order to accomplish this successfully, we wanted to build a complete DevOps pipeline, ensuring the application was being tested early and often: static analysis, unit, smoke, acceptance, security, feature, load, and performance. None of this testing was previously in place, and to ensure the refactoring doesn’t break anything, this testing became critical for us.
This session will discuss setting up a complete DevOps pipeline, with a quick CI cycle, followed by automated and scheduled CD cycles to QA, Staging, and Production. We will cover the many pitfalls of integrating already built code into this process, and some lessons learned and good strategies for other teams looking to accomplish this. Tools and techniques used for a PHP project will be demoed, but all of these practices can be applied to any project.