Container builds and automated deployment.
Make software delivery more repeatable.
Where this work fits
The services needed to run in development and production with their dependencies in place. Audio processing made that especially concrete: code could be correct while the deployed container lacked a required media tool.
I owned CI/CD work for development and production using Docker and AWS deployment services. I worked on packaging dependencies and automating release steps, reducing deployment issues and keeping the runtime aligned with what the application required.
Move a change through checks to release
Validate the change before releasing it.
An unchecked change does not replace it.
Check the change before releasing it.
A change passes through checks before release. If a check fails, the current version stays in place while the issue is fixed.
The runtime was part of the change.
A successful application build did not prove that the deployed worker had everything it needed. Container configuration and environment-specific settings had to travel through the release process alongside the code.
The skills behind the work
- GitHub Actions
- Automate repeatable checks and delivery steps around code changes.
- Docker
- Package an application with the runtime tools it needs to execute consistently.
- AWS
- Run and support cloud services behind the application’s operations.
Deployment issues decreased. The team had automated release steps and a more consistent runtime for operating the backend.