Building Stakeholder Confidence

Building Stakeholder Confidence

Confidence in:

  • Production is always up
  • Features will be built correctly

Exercises to Build Confidence

  • Build team-wide, deep understanding of each feature’s requirements and characteristics before coding starts
  • Expect collaborative, comprehensive grooming of features that include team and stakeholders
  • Ruthless slicing of features to smallest valuable increments
  • Write comprehensive automated unit tests in front-end and back-end layers
  • Shoot for high coverage from automated back-end integration tests
  • Shoot for high feature critical-path coverage from end-to-end UI tests
  • Include automated smoke tests that can be run on production-candidates
  • Ensure all post-commit tasks and hand-offs must be automated in CI/CD
  • Strive for quick, reliable rollback if smoke tests fail

Docker. How to get bash\ssh inside running container (run -d)?


$ sudo docker attach 665b4a1e17b6 #by ID
$ sudo docker attach loving_heisenberg #by Name
$ root@665b4a1e17b6:/# 

UPDATE: (docker >= 1.3) Thanks to WiR3D user who suggested another way to get container’s shell. If we use attach we can use only one instance of shell. So if we want open new terminal with new instance of container’s shell, we just need run the following:

$ sudo docker exec -i -t 665b4a1e17b6 bash #by ID
$ sudo docker exec -i -t loving_heisenberg bash #by Name
$ root@665b4a1e17b6:/#