7 Best Practices for Software Development with Mattermost Integrate CI/CD pipelines Continuous integration and continuous delivery (CI/CD) are considered best practices be - cause releasing small pieces of work regularly reduces firefighting and increases value for the end user. Automations like build processes greatly reduce the risk of introducing errors during deployment, support security best practices , and help the entire team stay on track throughout the build and release process. However, working with additional systems adds to the volume of tools a team needs to manage and monitor and leads to increased context switching and decreased productive time. Here are three ways to integrate your CI/CD pipelines so that you don’t need to leave Matter - most to trigger, monitor, and interact with workflows: 1. CircleCI - Connect your builds directly into Mattermost, then use integrat - ed commands to monitor pipelines and trigger workflows. Receive notifi - cations from CircleCI in Mattermost channels, and interact with the plugin using `/circleci` slash commands. 2. Jenkins - Similar to the CircleCI plugin, the Jenkins plugin allows you to subscribe to build notifications in Mattermost Channels, start jobs, get logs, restart servers, and lots more. You may also want the Jenkins post- build action plugin to send webhook notifications. 3. GitLab CI/CD - Include notifications about your GitLab pipelines using the Mattermost GitLab plugin to subscribe. This plugin includes a host of GitLab integration features for two-way communication with Mattermost. Run `/gitlab help` in Mattermost for more details. 4. Find more CI/CD plugins for Mattermost in the Marketplace