To break silos and improve availability, DevOps/Ops should be actively collecting useful feedback of prod env maintenance on a regular basis. Enable developers to easily access it and improve feedback loop together as a team effort.
The very first and most important part. What To Examine, Providing Developers Meaningful Feedback?
Occasionally DevOps code needs to check and wait status, before running further steps. For example, wait for service A to be up, then start service B; confirm TCP port is listening, then launch requests; etc.
For simplicity or time pressure, people usually use a blind wait like “sleep 10” to fix this. This is certainly not good enough. How we can improve this with affordable cost?
After a lot of effort and communication, finally the system deployment works! To guarantee a smooth deployment anytime, we enforce daily deployment test as a next step.
Surprisingly daily deployment doesn’t always succeed like we expect, even if no major changes*. More interesting, many failed tests are kinds of false negatives. So what are the obstacles? And how we can avoid them?
Lots of people are talking about CI/CD on the Internet. I wish I could learn the details what they really enforce? Quite disappointed, mostly I only see concepts, principles, and guidelines.
Yes, I know it depends on a lot of things. After supporting several projects, I DO believe there are some useful first-hand experience which are general and not that well-known. Enclosed is a Demo Jenkins.
PPT Sharing for personal understanding and judgement for DevOps