Blogs

2 min read

3 Ways Atlassian Tools Help You Avoid Common DevOps Mistakes

Jun 4, 2019 11:42:00 AM

Using Atlassian tools for your DevOps endeavor sets your teams up for success. While there are many challenges in a new DevOps implementation, the tools you use don't have to be one. A quick search will show you that there are many ways to fail at DevOps - it requires massive organizational change and lots of moving pieces to function, so getting started can be tough. It might be a painful process to initiate, but as we've seen, it's absolutely worth it. With that in mind, while you focus on the big questions (Like how in the world can I deploy daily/weekly/hourly?), the Atlassian stack helps you out in some ways you may not have even considered. With one (or all) of these questions out of the way, you can get back to focusing on what matters: the people and processes that you're revolutionizing.

Below are a few common DevOps mistakes that Atlassian can help you avoid:

1. Failing to Automate Effectively

Automation is an essential component of DevOps - and one of the hardest. Rather than finding one product that tries to do a million things well, with the Atlassian stack you've got the killer combination of several awesome products that integrate seamlessly. The native integrations mean that in just a few clicks, your Bitbucket branch creation or pull requests, your Crucible code reviews, or even your Bamboo builds can move your Jira issues through their workflow. This is essential when you're working with several different tools - trying to keep track of where the work is will slow you down and has the potential to delay important milestones. Additionally, while the Atlassian tools work together like one product, if your team uses an alternative to one of the options, you can integrate them as well with the same ease.

Don't let your work tracker become just another bottleneck - make sure your tools are effectively integrated and refocus your energy elsewhere.

2. Ignoring HA Principles

The best systems aren't worth much if they're not up. When you're committed to High Availability (HA), you need your systems to be up as much as you (and your users) are - avoiding single points of failure, focusing on redundancy, and immediate failure detection. Jira and Bitbucket Datacenter products provide high availability so you can trust your systems will be up when they need to be (which is to say, always).

3. Mishandling Incidents

DevOps isn't just deploying quickly, but managing your code in an intentional way. This means making sure that if something goes wrong, you know it. Jira Service Desk has built in automation to keep work up-to-date and moving through its lifecycle. When you pair that with real-time build information, accurate visibility into things like pull requests and open incidents, then staying up to date is a breeze. Tracking incidents and development work in the same tool means you don't have to jump between issue trackers to know what's going on, and you can set up Jira Software and Jira Service Desk to keep everyone on the same page.

You'll often hear that DevOps is too focused on tools, and that you need to refocus on people and processes. This is absolutely true - the key is to work with tools that help you get out of your own way so you and your team can Get S@!# Done.

To read more about how Atlassian works with DevOps, read DevOps + Atlassian = Doing it Right by Senior Consultant Michael Knight or Top 5 Ways Atlassian Facilitates DevOps by Bryan Robison, Principal at Praecipio Consulting.

Written by Morgan Folsom

Upcoming Webinars

Past Webinars

Case Studies

Blog