Talking Toolchains at Team Talks
When Atlassian launched Open DevOps, we were on a mission to help you build the best toolchain for your software delivery cycle - because you shouldn’t have to choose between best-of-breed or all-in-one.
In the fall of 2021, Team Talks brought together Atlassian customers and DevOps partners AWS, Snyk, Split, and Mabl to share tips, tricks, and trends to help teams ship better software, faster. This 5-part series is available on-demand - and each episode is 30 minutes or less - so you can streamline your toolchain and incorporate third-party apps into Atlassian products like Jira, Confluence, Bitbucket, and Opsgenie.
Whether you tuned in live to our Team Talks series or you haven’t had the opportunity to check it out, I’ve recapped some of the key components of Open DevOps and a few apps you might consider adding to your toolchain.
Is Open DevOps for me? 
User expectations and the speed of software deployment are constantly increasing. You want to provide the newest features and benefits to your customers as quickly as possible, but you can’t sacrifice quality in the process. This creates a potential bottleneck when it comes to QA.
In his Team Talks session, Dave Karow, Continuous Delivery Advocate at Split, talked about the benefits of progressive delivery - which deploys new versions of software to a subset of users before rolling out to all users. Through Split’s feature flagging tool, which integrates with Jira, you can control how many people see a new version at any given time, identify issues, and kill a feature flag if changes need to be made.
Another emerging DevOps trend, test automation, can help with the speed and quality of each deploy. Currently, only 12% of teams claim to have full test automation, which transitions QA from being a bottleneck in the development process to what Thomas Lavin, Product Manager at Mabl, calls a “watchful eye.” Automated testing allows you to create and manage reliable tests for the entire user journey - it’s estimated that tests are conducted seven times faster and with 40% fewer bugs.
So how does this work as part of Atlassian Open DevOps? By integrating automated testing through Mabl with Jira, you can escalate failures in just a few clicks, which takes the back and forth out of defect reporting. Diagnostic data appears automatically in Jira, creating a single source of truth so your team has all of the information needed to resolve the failure.
Keeping security top of mind 
Open DevOps goes beyond simply speeding up the software development process - after all, what good is a new feature if security is a concern?
To make sure Atlassian users keep security a top priority, you’ll find a Security tab within Bitbucket Cloud that offers a native integration with Snyk. Snyk is a developer-first solution that shows real-time vulnerabilities in a repository. In his Team Talks session about security vulnerabilities, Marco Morales, Partner Solutions Architect at Snyk, explained how to use Bitbucket Cloud to see the number of current vulnerabilities as well as how how critical each vulnerability is and how to fix it.
But it doesn’t end there. Within each vulnerability, you can create a Jira issue that automatically populates data from Snyk so your team has everything they need to triage and make the fix.
How do I get started?
I’m so glad you asked!
Atlassian Open DevOps is incredibly easy to get up and running, and the best part is you can try it for free. Simply create an account and you’ll get Jira Software, Confluence, Bitbucket, and Opsgenie out of the box. Then you can select which tools you want to add to your toolchain - our DevOps partners cover everything from security to feature flagging, observability, and testing. And because this is a truly open solution, you can also pull in any other existing tools your team uses.
If you want to learn more about how to get started with Atlassian Open DevOps or any of the integrations I mentioned, our Team Talks series is available on-demand anytime!
Was this helpful?
Thanks!
Kim Bratek
1 comment