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!
Delivering short and precise documents quickly is a key asset for DevOps. Nowdays, hosting code in GitHub is not only fancy but also overwhelming. Consequently more and more documentation effort goes to GitHub.
As a late fanboy of Atlassian Confluence, I also make my preference in GitHub wiki now. Enclosed are tips for how to do effective documentation in GitHub.
Sandbox indicates an isolated and autonomous play-yard, where anyone can do their own code build, deployment and debugging locally. It won’t effect anything outside. Ideally it should not be effected by outer world either. This is especially useful for new member on-board, daily development, QA cycle, etc.
How to get an easy and reliable sandbox for your projects? Check it out.