Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Your life wouldn't be interesting without the enterprise firefighting 😉
Containers make these problems go away in large part. Becomes much easier to achieve consistency and show the problem isn't you.
kai1879732d@SortOfTested Yes! That's true! But the problem here is, we move all our build artefacts to a centralised repository, from there any bare metal server or container can subscribe to it and the build will be delivered to that server. It's that config that fucked up! It was sending the older version of the build, while we had specified the newer version, had to manually point to the new version. Not sure why it happened though
Containers contain the build artifacts, that's their key value propsition. The fs doesn't change at runtime, or pull any resources. The container build file will pull the code, builds it and your build server pushes it to a registry.
Orchestration then picks up your latest push and can be set to update your container using a deployment automatically based on the build version.
Take the humans out of the equation, reduce the entropy in the system. Works every time. 😘