Overview of Atlassian Open DevOps

Summary

Gareth, a product manager at Atlassian, introduces 'Atlassian Open DevOps', a flexible toolchain experience for the entire software delivery lifecycle. It integrates Jira Software, Bitbucket, Confluence, and Ops Genie, with the option to swap in other tools like GitHub or Jenkins. The platform aims to eliminate the compromise between best-of-breed and all-in-one toolchains, offering seamless integration and coordination for teams to focus on delivering value to customers. Open DevOps promises to simplify the complexity of tool integration, provide automation capabilities, and enhance the software delivery process.

Takeaways

• 🚀 Atlassian Open DevOps is a toolchain experience designed for the entire software delivery lifecycle, offering flexibility and coordination across multiple tools.
• 🔧 Open DevOps aims to solve the dilemma between best-of-breed and all-in-one development toolchains, allowing teams to use their preferred tools without sacrificing integration.
• 🛠 The default tools in Open DevOps include Jira Software, Bitbucket, Confluence, and Ops Genie, but teams can swap in other tools like GitHub, GitLab, Jenkins, or CircleCI.
• 🔄 Open DevOps is built to be connected with any tools used in software development today, with existing integrations for testing, security, feature flagging, and observability in Jira.
• 📈 Access to Open DevOps is obtained by signing up at atlassian.com, which automatically provisions and connects free versions of the core tools, with the option to upgrade or swap them out.
• 📊 Jira serves as the central hub in the development toolchain, with features like code, deployments, on-call, and pages automatically connected to other Atlassian products.
• 🛑 Users can easily toggle features on and off in Jira to customize the toolchain to their team's needs without being overwhelmed by irrelevant tabs.
• 🔗 Open DevOps facilitates seamless integration between Jira and other tools, such as Confluence for documentation and planning, enhancing team collaboration.
• 📝 The development process is streamlined with Jira's issue tracking and workflow management, supporting custom workflows to match team practices.
• 🔑 Automation capabilities in Jira are highlighted, allowing teams to create workflows that keep work in sync with development activities, saving time and reducing manual updates.
• 🌐 Future enhancements for Open DevOps include reducing friction for third-party app integration and bringing more of the development cycle directly into Jira.

Q & A

What is the main focus of Atlassian Open DevOps?

Atlassian Open DevOps is a toolchain experience for the entire software delivery lifecycle, designed to provide flexibility and coordination across multiple tools, allowing teams to work with their preferred tools without sacrificing integration.

Why did Atlassian create Open DevOps?

Atlassian created Open DevOps to address the dilemma companies faced between using best-of-breed tools or an all-in-one solution. It aims to eliminate the compromise between having a disjointed best-of-breed toolchain and settling for 'good enough' tooling.

Which Atlassian products are central to the default Open DevOps project?

The default Open DevOps project is built around Jira Software, Bitbucket, Confluence, and Ops Genie.

Can teams use tools other than Atlassian's in Open DevOps?

Yes, teams can swap in the tools they are already using, such as GitHub, GitLab, Jenkins, CircleCI, or any other tool, into the Open DevOps project.

How does Open DevOps handle integration with third-party tools?

Open DevOps is designed to be connected with any tools used for software development today, with existing integrations for testing, security, feature flagging, and observability vendors in Jira for Open DevOps.

What is the process for getting access to Open DevOps?

To get access to Open DevOps, one would sign up at atlassian.com/solutions/devops. Upon signing up, free versions of Jira Software, Bitbucket, Confluence, and Ops Genie are automatically provisioned and connected.

How does Open DevOps support teams in managing their development process?

Open DevOps supports teams by providing a hub in Jira, where they can manage their development process, track work, and integrate with other tools like Confluence for documentation and Bitbucket for code management.

What is the role of Jira in the Open DevOps toolchain?

Jira serves as the hub of the development toolchain in Open DevOps, centralizing the management of issues, tracking work, and integrating with other Atlassian products and third-party tools.

How does Open DevOps facilitate the connection between code development and issue tracking?

Open DevOps allows for automatic linking of development work to Jira issues by including issue keys in commits, branches, or pull requests, which then appear on the Jira issues.

What features does Open DevOps offer to streamline deployments?

Open DevOps offers a deployments page that automatically tracks issues with commits through to deployment, providing a clear timeline of what value has shipped to customers and when, across any CI/CD provider.

How does Open DevOps address on-call responsibilities for teams?

Open DevOps integrates with Ops Genie to display the on-call schedule to the entire team, ensuring that everyone knows who to contact when issues arise with the services or deployments.

What automation capabilities does Open DevOps provide?

Open DevOps offers automation capabilities through Jira's automation engine, allowing teams to create powerful workflows across all their development tools, keeping work in sync with development activity and saving time.

Outlines

00:00

🌐 Introduction to Atlassian Open DevOps

Gareth, a product manager for DevOps at Atlassian, introduces the concept of Atlassian Open DevOps, a toolchain experience designed to cater to the entire software delivery lifecycle. Open DevOps is built around Atlassian's core software tools and extends to partner tools, allowing teams to work in their preferred tools without losing coordination. The platform addresses the dilemma companies face between best-of-breed and all-in-one development tooling. Atlassian aims to provide flexibility, supporting multiple tools and integrating them seamlessly, thus eliminating the need for compromise. Teams can focus on delivering value to customers while Atlassian handles the complexity of tool integration. Open DevOps is designed to be adaptable, with the default project including Jira Software, Bitbucket, Confluence, and Ops Genie, but also allowing for the integration of other tools like GitHub, GitLab, Jenkins, or CircleCI. The platform offers pre-built integrations for testing, security, feature flagging, and observability vendors within Jira for Open DevOps. Future plans include reducing friction for third-party apps and incorporating more of the development cycle into Jira.

05:01

🛠️ Utilizing Atlassian Open DevOps for Team Workflow

This paragraph delves into the practical application of Atlassian Open DevOps within a team's workflow. It starts with using Jira's roadmap and feature tracking to create an epic for development. Confluence is highlighted as a tool for brainstorming and creating spec pages, which can be easily referenced from Jira. The importance of issue management in Jira is emphasized, with issues serving as discrete units of work, including stories, bugs, and feature requests. The paragraph also discusses the integration capabilities of Open DevOps, allowing teams to work in their preferred development tools while minimizing the need for status updates and context switching. The script demonstrates how to link development work with issues in Jira, using the development and releases panel and the code page to provide an overview of repositories and their relation to Jira issues. The deployments page is introduced as a way to track code shipments to production across any CI/CD provider, offering a clear view of what value has been shipped to customers and when.

10:02

🔧 Atlassian Open DevOps: On-Call Scheduling and Automation

The final paragraph of the script focuses on the operational aspects of Atlassian Open DevOps, particularly on-call scheduling and automation capabilities. It explains how the on-call schedule can be managed and displayed to the entire team through Ops Genie, ensuring that everyone knows who to contact when issues arise. The paragraph also highlights the automation features within Jira's automation engine, which allows teams to create powerful workflows across their development tools. Two specific automation rules are showcased: one that transitions an issue from 'In Progress' to 'In Review' upon the creation of a pull request, and another that moves an issue from 'To Do' to 'In Progress' when a commit is created. These automations help to keep work in sync with development activities and save time by reducing the need for manual updates. The script concludes by encouraging teams to try out Atlassian Open DevOps and explore its capabilities, with a promise of continued improvements and integrations in the future.

Keywords

💡DevOps

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the system development lifecycle and provide continuous delivery of high-quality software. In the video, DevOps is the overarching theme as it discusses the Atlassian Open DevOps tool chain, which is designed to facilitate the entire software delivery lifecycle.

💡Product Manager

A product manager is a professional responsible for guiding the development of a product, from its conception to delivery. Gareth, the speaker in the video, is a product manager for DevOps at Atlassian, and he introduces and explains the Atlassian Open DevOps tool chain.

💡Tool Chain

A tool chain in software development refers to a sequence of software development tools that are connected to form a complete development process. The video discusses the Atlassian Open DevOps as a tool chain experience that integrates various software tools to support the entire software delivery lifecycle.

💡Jira Software

Jira Software is a project management tool used by agile teams to plan, track, and manage their work. In the context of the video, Jira Software is a core component of the Atlassian Open DevOps tool chain, serving as the hub for development teams to manage their projects and track progress.

💡Bitbucket

Bitbucket is a web-based version control repository hosting service for source code and development projects that support Git. It is mentioned in the video as one of the default tools in the Atlassian Open DevOps project, used for code management and integration.

💡Confluence

Confluence is a collaboration tool used to help teams collaborate and share knowledge. The video describes how Confluence is integrated into the Atlassian Open DevOps tool chain, allowing teams to create and reference documentation directly from Jira.

💡Ops Genie

Ops Genie is an incident management and on-call scheduling tool that helps ensure the right people are alerted to critical issues at the right time. The video mentions Ops Genie in the context of the Atlassian Open DevOps tool chain, highlighting its role in displaying on-call schedules within Jira.

💡Integration

Integration in the context of software development refers to the process of combining different software components or tools to work together. The video emphasizes the integration capability of the Atlassian Open DevOps tool chain, allowing teams to connect and use their preferred tools seamlessly.

💡Automation

Automation in software development refers to the use of tools to control and monitor the software delivery process without human intervention. The video showcases the automation capabilities of Jira's automation engine within the Atlassian Open DevOps tool chain, which helps to streamline workflows and reduce manual updates.

💡CI/CD

CI/CD stands for Continuous Integration and Continuous Delivery/Deployment, which are practices in software development that aim to improve the process of integrating changes from multiple contributors into a single software project. The video mentions various CI/CD providers such as Bitbucket Pipelines, Jenkins, and CircleCI, which can be integrated into the Atlassian Open DevOps tool chain.

💡Third-Party Apps

Third-party apps refer to software applications that are developed by a company or individual outside of the main software ecosystem. The video discusses the future plans of Atlassian to reduce friction for starting with third-party apps by adding them as one-click connections to Jira within the Open DevOps tool chain.

Highlights

Introduction to Atlassian Open DevOps: A tool chain experience for the entire software delivery lifecycle.

Atlassian Open DevOps integrates core tools like Jira Software, Bitbucket, Confluence, and OpsGenie, while allowing flexibility with third-party tools.

Solves the dilemma between best-of-breed and all-in-one development tools by offering integration without sacrificing coordination.

Enables teams to work in their preferred tools without compromising on functionality or coordination.

Offers automatic provisioning and connection of free versions of core tools upon signing up for Open DevOps.

Supports integration with popular third-party tools such as GitHub, GitLab, Jenkins, and CircleCI.

Includes features for testing, security, feature flagging, and observability, all integrated within Jira.

Future plans to further reduce friction with third-party apps and bring more development cycles directly into Jira.

Provides a demo content and quick start guide in Jira to help users get oriented with the tool.

Jira serves as the hub of the development tool chain, integrating code, deployments, on-call schedules, and more.

Easy toggling of features on and off to customize the tool chain according to team needs.

Automatic tracking and display of development information and deployment status in Jira.

Integration with OpsGenie to display on-call schedules, ensuring teams know who to contact during issues.

Powerful automation capabilities within Jira to streamline workflows and reduce manual updates.

Encourages users to explore and customize Open DevOps to fit their unique development processes.

Future enhancements will include easier third-party app integrations with one-click connections in Jira.

Transcripts

hey everyone

i'm excited to be with you today um my

name is gareth i'm a product manager for

devops here at atlassian

and today i'm going to be doing a deep

dive into

atlassian open devops a tool chain

experience for the entire software

delivery lifecycle

it's built around our core software

tools but extends to our partner tools

so teams can work how they want in the

tools they want

without sacrificing coordination

so we built open devops because the

decision that

a lot of companies faced was for their

development tooling was either best of

breed

or all-in-one which felt like an

ultimatum

we would see companies consolidate all

their tools into a single vendor

and resign themselves to a disjointed

best-of-breed tool chain

the tool consolidation results in teams

settling for good enough tooling

and ways of working instead of great at

atlassian we believe

that the best development tool chains

require the flexibility to support

multiple tools with the launch of

atlassian open devops it's no longer a

compromise

teams that build software can focus on

shipping value to their customers

while we take on the complexity of

integrating the tools

of choice and making sure that their

work just flows

so introducing atlassian open devops

the default devops project in open

devops is built around

jira software bitbucket confluence

and ops genie however teams can swap

in the tools they're already using

whether that's github or gitlab

or jenkins or circle ci or any other

tool that the team is using

just like there's no one way to do

devops there's no one tool chain that

works for all teams

open devops is meant to be connected

with any of the tools that

is used for software development today

we already have integrated integrations

with

testing security feature flagging and

observing

observability vendors in jira for open

devops

in the future we will be removing the

friction to get started with third-party

apps enduro

and bringing in more of the development

cycle directly into jira

we want to make sure your best of breed

tool chain feels like an all-in-one

so in order to get access to open devops

you'd sign up for open devops at

atlassian.com

solutions slash devops when you sign up

for open devops we'll automatically

provision and connect free versions of

jira software

bitbucket optioni and confluence and you

can upgrade these tools

individually anytime or swap them out

for third party tools of your choice

if you're an existing customer you can

head to atlassian.com

solutions slash devops and we'll

provision and connect the tools that you

don't have

already if you already have tools

connected that you want to use

then no worries you can create a new

project

up to make it connected and we'll prompt

to link

you together the appropriate containers

such as your repos or your spaces

so for instance if you already have

github or confluence you can link their

containers at the point of project

creation

okay so now i'm going to walk you

through a

demo okay let's walk through what

happens when you've created your project

so once you've done that you'll land in

jira with some demo content

to help you get oriented we've loaded

your jira project with demo issues

and a quick start guide to get you

orientated which you can see

here on the right hand side in addition

we've automatically turned on features

like code

deployments on call and pages and

connected

it to the other products in atlassian

open devops

here you can see that jira is really the

hub of your development tool chain

if you don't need uh certain features

you can easily toggle them off uh in the

features page

this will remove them from the

navigation so your team aren't confused

with

irrelevant tabs but you can also just

toggle them back on

in the future okay let's take a look

at what it might look like to use

atlassian open devops across your team

so imagine your team is tasked with

shipping and

operating an application and as a team

lead you'll be managing the process

so you can start with jira's roadmap

feature and to create an epic for the

development

you can see here's one that i created

earlier

um and while you your um

team will use jira to break down and

track the work

uh they might also use confluence to

brainstorm and create

spec pages you can easily access

confluence and the rest of the products

in open devops

directly via the app switcher

so as you create pages in confluence

you can easily reference it from jira by

clicking on the

on the pages tab here so if i go ahead

and

click confluence

here you'll see the pages that we

automatically

uh created in confluence

making it easy for your team to get the

full context of what's going on

and confluence has a bunch of templates

to help you get started with your work

um such as change management

templates run books and post in incident

reviews

so let's hop back to jira

open devops project

so let's say you've planned your bigger

roadmap you've written your specs

and you're ready to start development

work your dev team likely plans and

breaks down their work

into issues and issues are discrete

units of work that include things like

stories

and bugs feature requests etc

you can use the default workflow in jira

to create your own

or create your own by adding additional

columns uh

to the board um and you can see some of

the

additional columns that i've added to

this board here

use the board to create issues that help

you prioritize

and track your work

so your development team likes to work

in their co-tool of choice

um but the business is running on on

jira

so open devops is built to give you the

best of

both worlds by bringing together that

development context

in jira and minimizing the needs for

status updates

and context switching so let's see how

we

uh you'll be able to tie your code that

your developers are working on and

shipping

with the work uh issues

in jira

so if i open this issue here

you can see that on the right hand side

there is this development and releases

panel

so as long as your development team are

including issue keys in

your commits branches or pull requests

this development information will

automatically

appear on these juror issues

in addition to that we also have the

code page

so i click into that code page um

this is a page that anyone on the team

can get

can use to get an overview of the

different repos

that the team is working across it's

automatically

surfaced right in jira as long as again

your

team is including issue keys in their

commits and

pull requests jira will automatically

pass out

their repo information and display it on

the page

so all software teams ship code

which is why we built this deployments

page

so as long as um your

development team are in the habit of

using issue keys in their commits

jarrett will automatically track those

issues with those commits

through to them being deployed it will

populate that information on this

uh deployment timeline as you can see

here

um and so you no longer have to ask the

team

what what is shipped has that feature

being shipped yet

or not you can come here and get a real

sense for that

you can also filter um this view by

um by different things so we've added

environment epic and the type filter

so if there's specific environments or

specific

epics or even issue types that you care

about you can go

and filter this view by those by those

things

so deployments interior surfaces all the

deployment information

showing what value has shipped to

customers and when across

any ci cd provider so from bitbucket

pipelines to

leading third-party vendors such as

jenkins as your devops

circle ci octopus deploy and jfrog

now your team has shipped

um value to customers and ships

things to production you're probably

wondering who's on call for the for

those services and those things that

that you've just deployed and this is

where the uncle um schedule comes in

so uncle um tab and page

syncs directly with ops genie to display

the on-call schedule to the entire team

so that they know who to contact when

things break

not that they ever do of course

cool and then lastly i want to show you

the

automation um capabilities that we have

which i'm sure a lot of you will will

find valuable

there's lots of opportunity um to

automate

processes and teams using open devops

can create powerful workflows across all

of their development tools

with jira's automation engine keeping

work in sync

with development activity and saving

time for everyone

so if i go to automation

action at the top right hand side on the

board and we'll go to

manage automation rules

you can see here that i have already

created two

automation rules so let's go and have a

look at this

one here so with this first automation

rule

and we've configured it to respond to a

pull request

trigger so what this is doing

is that when i create or the team

creates a

pull request then it transitions the

issue from

in progress to in review

again negating the need for um for that

manual intervention and those manual

updates

and here's another example of an

automation that i've set up

and this is responding to a a commit

created

trigger so when that commit is created i

i transition the issue from to do to

in progress again just another example

of

um automation options that you have with

uh

with our automation capabilities here

for endura software

so automation rules are really great in

removing the need for

for manual updates and just generally

overall improving your software delivery

process

there's plenty more to dig into but we

think the best way of getting to know

atlassian open devops is by trying it

out

out for yourself to learn more about the

other products

in open devops we recommend checking out

the individual product demos on our

website

we're excited to see how your teams will

use customize and extend

open devops and even more importantly

we're excited to see what you build with

it

in the future we'll continue to make it

easier to get started with third-party

apps by adding them as one-click

connections to jira

in future milestones get started with

open devops today by visiting

atlassian.com

solutions slash devops

and that's a wrap thank you for taking

the time to allow me to deep dive into

atlassian open devops

you