Videos  /  AnsibleFest London 2016  /  Atlassian

Continuous deployment is causing organizations to rethink how they build and release software. Atlassian is adopting this model throughout the company, but not all teams have the same challenges to overcome in doing so. Steve Smith lead the team that converted the company's critical order-processing system from a monolithic, single-server application to a continuously-deployed, high-availability platform. Along the way there were a lot of practical and organizational issues that needed to be addressed in adopting this development model; in this presentation he shares some of the experiences and lessons of doing so.

This talk covered continuous deployment from a number of different angles; high-availability requirements, development processes (in particular git-based branching workflow), practical delivery technologies (including analysis of the trade-offs), and organisational considerations and bottlenecks (e.g. SOX/PCI compliance issues).

  • The background to why you may adopt CD
  • The bottlenecks and trade-offs you have to take into account
  • Development workflows to support CD
  • The technologies and practicalities of actually performing CD in the real world


Steve Smith


Steve Smith, Developer Advocate, Atlassian

twitter linkedin