DevOps To NoOps: The JIRA Development Team's Journey to NoOps Freedom
summary
Atlassian moves from DevOps toward NoOps by making product teams self‑service: CI artifacts flow from commit to release, release steps are push‑button and release notes are auto‑generated into Confluence. The inner loop has 3,000 functional tests that originally take three hours, split across 15 parallel build runners to cut feedback to ~40 minutes; artifact passing avoids recompiles. The stack uses Bamboo + Nexus + EC2 + Puppet (KVM on‑prem agents, Maven, Selenium). Cost and scale work: EC2 spot instances and automation halve infra cost and enable automated, repeatable releases.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:34Performance Tests
- 13:14Bamboo Staging
- 13:38Ci Process and Structure
- 15:36Performance Improvements
- 23:29Maven Release Plugin
- 27:23Clone an Issue in Jira
- 28:31Automate the Generation of Our Release Notes
- 31:03Why Do We Choose Kvm
- 32:21Why Amazon Ec2
- 34:11Cost of Amazon
- 40:09Source Control
- 40:46Why Nexus and Great Maven Dependency Management
- 42:15Make Changes to Infrastructure with Confidence
- 48:50Workflow
related talks
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
26mDevOps and Lean in Legacy Environments
05mBrownfield DevOps
24mHow DevOps changed the way we operate software
38mDevops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach
01h 01mA team's transition to Continuous Delivery
30mA Story of DevOps Transformations
37mDevOps for Java Developers (Or Maybe Against Them?!)