Deployments

This is a continuation of the post, which details into the working of vesemir and how it goes about introducing changeset. Give it a read before continuing reading this, to allow you to gather more context on the what and the why. While this post will focus more more on how we went on with revamping vesemir for increasing it’s reliability, maintainability and modernizing it. Continuing the thread around how we did the same for Vesemir. (1/n) https://t.co/Xol0uRraJv ...

This post is a continuation of the tweet here The build and deployment pipeline for each org will be different in some way or the other, given each co will have it’s own requirements. This thread talks a bit about our virtual machine deployment pipeline (1/n) — Tasdik Rahman (@tasdikrahman) June 10, 2021 This was also cross posted originally for the gojek tech blog https://www.gojek.io/blog/introducing-vesemir-gojeks-virtual-machine-deployment-service The build and deployment pipeline for each org will be different in some way or the other, given each co will have it’s own requirements. Even in my last org, the way our team enabled other teams to ship code/config changes, was pretty different from the way we do it in my current org. ...