When dealing with release management, you can leverage our maintained GitLab and GitHub plugins to communicate with your source control within Mattermost. Similarly, you can configure inbound webhooks or add popular plugins and apps (more on that in a moment). By creating slash commands easily in the Integrations menu, you can add clickable buttons to your playbooks that trigger any webhook process. You must also equip the team with the tools they need for the task at hand. Extending your playbook with slash commandsīut organizing people and messaging for a shared purpose is only one part of the challenge. You’ll also be able to add participants and stakeholders on the fly, depending on the situation at hand. The Playbook will organize all of that information so everyone is on the same page. Gone are the days of wondering what’s going on or what needs to be done and by whom. When coordinating between teams to release software, this ad hoc and contextualized channel is a great way to immediately put everyone in one spot and assign an appropriate agenda. You can start from a very simple process and scale up as you discuss new discrete tasks that need to be replicated each time.īecause you’re using Playbooks, each release management run will keep all related team messages in its one dedicated channel. For that reason, don’t get stuck thinking about every situation upfront.
The playbook can be edited within each run in real-time, so think of this checklist as a living document that you can adapt on the fly. The pre-built release management template has a general release flow and suggests some ways you might want to incorporate your process, but starting from a blank template and incrementally building what you need is also an effective approach, depending on the scale of your release process. To get started, create a Playbook from either the Product Release template or the blank template. Setting up a playbook for release management
0 kommentar(er)
