Operations | Monitoring | ITSM | DevOps | Cloud

Does Your Team Need a Quality Assurance Engineer?

When you develop software solutions, code quality and security are of top importance, and can often define your success or failure. Some teams may require a specialist constantly checking software for bugs and issues, especially when the project is large and unrevealed bugs can have costly consequences. For small development teams or early project development stages, developers may try to work without a quality assurance engineer and test everything themselves.

Join the Mattermost mobile beta program: v2.0 is now live!

Get ready for the future of Mattermost mobile. Beta testers can now access Mobile v2.0, including multi-server support — our most requested mobile feature ever. We’re also bringing you a number of usability enhancements and performance improvements to make you productive on the go. If you want to be on the cutting-edge of Mattermost mobile development, we’d encourage you to join the mobile beta program today.

Featured Post

Imagining the Future of Engineering: Insights from top women in tech

This International Women in Engineering Day, the theme is #imaginethefuture. Supporting women in engineering, now and in the future, is vital as it allows us to develop inclusive, innovative solutions for complex issues that can benefit everyone. We have collated the thoughts and opinions of the specific challenges that a number of females across the tech industry have faced, as well as, providing advice for other women looking to break into the industry.

Jira GitHub Integration

You can create a Jira GitHub integration through Git Integration for Jira. This tool will allow you to use smart commits, create branches and pull requests on your GitHub repositories directly from Jira, index repositories with webhooks, and more! Developed by Atlassian in 2002, Jira is a project management tool that aims to help software development teams effectively track their projects.

Tech Ops is a mess. Here's why we're committed to fixing it.

Building software is hard. Building cloud software is even harder because things move much faster — and require mission-critical reliability and availability. To effectively build software in the cloud, engineering teams need observability, CI/CD, reporting, and lots of tooling. At every organization I’ve worked at, we’ve needed a system of tools that lets us: But all the tools available to engineering teams never quite fit together with our specific processes.

Mattermost Playbooks How-to: Software Feature Development

For teams that follow a structured build and release cycle, having a reliable, shared workflow makes the difference between chaos and consistency. With every new feature in development the team needs to know what the specs are, how it fits in the roadmap, what the customer feedback was, where to find the repository, who is responsible for each step, and so much more.

Mattermost Playbooks How-to: Release Management

Releasing software to users has become a sophisticated and intricate process that requires high levels of consistency and coordination. A release has to be built, brought together, documented, tested and deployed, which requires coordination of at least four separate teams and a generous handful of pipelines and other tools. Without a well-documented process things can get messy very quickly, causing stress for everyone involved.

Mattermost Playbooks How-to: Incident Resolution

Whether you’re part of a team managing SaaS products or a high-security digital workspace, sometimes Things Go Wrong and must be addressed with extreme care, professionalism, and predictability. For outages, data breaches, vulnerabilities and more, you and your team are juggling a variety of tools, processes, and rigid incident management systems. When the on-call pager goes off at 3 am almost no one has the ability to remember every step needed to kick off all the response workflows.