4 ms·
We use containers to reduce the testing surface and enforce standards. And if course to ease testing as we now transition the same build through dev, staging an
by tyldum 8y ago
We use containers to reduce the testing surface and enforce standards.
And if course to ease testing as we now transition the same build through dev, staging and prod.
The devs just have a single base container to work off from and we use CICD to further enforce whatever we need to.
It also makes it easier for devs to propose changes, as we know we can consistently apply them.
- haskellandchill 8y agoYou can use them to do that but is it working? That was the point, I also agree that no, it is not working and has rather introduced several layers with painful and hard to debug failure modes.
- taeric 8y agoA problem comes down to answering questions such as "exactly what versions of X are installed in our beta stack?" Usually trivial if X is part of your application. Much more complicated if X is some lib that is on the system/image.