The way I like to deploy a Smalltalk backend service is when developers have their cloned git repos and follow gitflow, one new directory for a new branch, so t

The way I like to deploy a Smalltalk backend service is when developers have their cloned git repos and follow gitflow, one new directory for a new branch, so they can: 1. Build a local image intended to help with 1 branch (branched out of fresh cloned develop). 2. Add changes, unit and system tests for TDD/regression defense/coverage. 3. Commit and push code to share with the teammates. 4. Open PR to develop when ready/PR's approved 5. Eventually merge develop into master and version bump for release 6. The PRs running CI/CD pipelines with the full battery of tests and 7. The final docker image that devops can consume at will for deployment under their load balancer or whatever architecture they had setup. In this style, images generated by work on bugfix or feature branches are optionally disposable after its PR. The dev can choose to archive or not.