Following git workflows, there is a branch called activesprint, or develop. It is the release candidate. Most of active branches should base on it.
Team need to be notified, whenever a new activesprint branch has been created. To lower the communication effort, we can automate the detection process and get slack notifications.
Has the deployment been initiated? Already finished? And how does it look after the deployment? These are typical questions people will frequently ask. Especially managers and key holders.
Thanks to Slack, team can sync up much easier than before. With more and more DevOps adoptions, we’re likely to have one-button click deployment.
Let’s send out slack notifications for system upgrade. Better sync up, better control.
Never Turn DevOps Interview Into Quiz. Find people who are positive and happy, with a focus on self-improvement, who have gratitude, are humble and comfortable with extreme transparency.
Here are some handy guidelines and open questions!
Effective and meaningful communications always lead to good results. However communication of TOI (transfer of information) should be avoided as much as possible. As a DevOps engineer, I used to get messages like this, “Hi Denny, I’ve changed XXX. Please check and make proper change on your side”.
Why it’s not good to rely on human communication for TOI? Firstly people will forget, which means expected collaboration will be ignored. Secondly human intervene and communication really takes time for both sides. So How We Can Improve This?