Transforming software shipping through continuous integration and delivery
When I joined Qwilr, one of the first tasks I undertook was fixing a build
pipeline. It was still pretty minimal back then. We had a simple bitbucket pipeline build that had some
tests, but it had been abandoned at some point, and didn't get run. While that first step was a small
one, 5 years later we had a sophisticated testing and CD pipeline. We were able to ship code to
production multiple times day triggered by pull request merges.
All of this happened by evolving a build and deploy pipeline over time. The key tools we used were Docker, Buildkite, AWS, various test systems like cypress and jest. The details of this are length and intricate, but the impact on developer productivity was profound. They were able to focus on their work, and have confidence that their code would be shipped to production in a safe and reliable way, as well as shipping more regularly and easily. I truly believe shipping is the lifeblood of engineering teams.
The learnings from this process were many and hard won, and I can bring these many years of experience to your team.
All of this happened by evolving a build and deploy pipeline over time. The key tools we used were Docker, Buildkite, AWS, various test systems like cypress and jest. The details of this are length and intricate, but the impact on developer productivity was profound. They were able to focus on their work, and have confidence that their code would be shipped to production in a safe and reliable way, as well as shipping more regularly and easily. I truly believe shipping is the lifeblood of engineering teams.
The learnings from this process were many and hard won, and I can bring these many years of experience to your team.