Atlassian faces the same issues as any other software company in the world. The battle for continuous integration glory is fought every day, and at stake is nothing less than our development and delivery speed. Join us to find out how we do it at Atlassian, powered by Bamboo. Because in the Game of Codes, you win... or you die.

1. Games of Codes, the CI battle
A view behind the Atlassian curtains
ESTHER ASENJO • BAMBOO DEV TEAM LEAD • ATLASSIAN • @STHREO

2. Who am I?

3. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
THE CD BATTLE, AT ATLASSIAN
CONCLUSION

4. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
THE CD BATTLE, AT ATLASSIAN
CONCLUSION

5. Continuous Integration is a software development
practice where members of a team integrate their
work frequently.
Each integration is verified by an automated build to detect integration
errors as quickly as possible. This leads to significantly reduced integration
problems and allows a team to develop cohesive software more rapidly.
”
“
- MARTIN FOWLER, THOUGHTWORKS

6. do it FASTER.
make us STRONGER.
make it BETTER.
work it HARDER.

7. FASTER delivery.
STRONGER teams.
BETTER quality.
HARDER processes.

8. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
CONCLUSION
THE CD BATTLE, AT ATLASSIAN

9. Atlassian, a software company
Products Services
Ecosystem
Questions for Confluence
Team Calendars for Confluence
Share Point Connector for Confluence
www.atlassian.com
my.atlassian.com
Atlassian Account
JIRA Service Desk
JIRA Core
JIRA Software
Portfolio for JIRA
Capture for JIRA

10. Continuous Integration
is a battle.

15. The Continuous Integration battle,
IT DOES NOT COUNT UNTIL IT’S SHIPPED

16. When you play the Game of Codes,
you ship or you fail.

17. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
CONCLUSION
THE CD BATTLE, AT ATLASSIAN

18. Infrastructure

19. Tools

20. Processes

21. People

22. Infrastructure

23. Build Infrastructure
Engineering Collaboration JIRA family Dev Tools
Internal
Ecosystem

24. Collaboration JIRA family Dev Tools
Internal
EcosystemEngineering
Build Infrastructure
Build Engineering
Build infrastructure
Maven repositoriesRemote agents
Elastic agents
12
Bamboo instances
1200elastic agents 20 AMIs
4
remote agents
3,5k
build plans
15Nexus instances
14k
branch build plans

25. Tools Processes

26. Processes Tools : The CI anatomy
Developer Test DeliverBuildCommit


27. Developer Test DeliverBuildCommit

Processes Tools : The CI anatomy

28. - CONTINUOUS DELIVERY (ADDISON-WESLEY), JEZ HUMBLE AND DAVID FARLEY
Continuously is more often than you think.
”“

29. Confluence pipeline
































30. 100
developers
320
commits/day
20,000
tests
435
build plans
Confluence pipeline
1,5 days

31. I’m not slacking off,
my build plans are still running.
“
”
- ME

32. I’m not slacking off,
my build plans are queued.
“
”
- DANIEL KJELLIN, BAMBOO DEVELOPMENT TEAM LEADER
I’m not slacking off,
my build plans are

33. CI challenges our processes
Master branch production-ready Feature branch development
Long running branches
Big&slow test suite
Quick feedback
Feature flags
Build grid
Build strategy

34. Confluence pipeline strategy
30 min
Core
Test Suite
90 min
Cloud
Test Suite
Ecosystem testing
1,5 days
Full Test Suite
Performance testing
Cross-Platform testing
Acceptance testing
Confluence team
dog fooding
1 per day
1 per week*
Atlassian
dog fooding
Monthly bug fixing
Server release
Quarterly release
Cloud release
Every 2 weeks*
+ +++ =

35. The continuous integration pipeline stages
Commit Automated
testing
technically
functionally
non-functionally
usable
provides value
deliverable
fully-operational
Manual
testing
Release

36. The continuous integration pipeline stages
Commit Automated
testing
ReleaseManual
testing
QA
Dog fooding

37. 817quarantined tests
out of > 200k test

38. 1,888
occurrences of flakiness
in our Confluence wiki

39. But hey: I am code too, you know?
I need attention!
“
”- MAURI EDO (@MAURI_EDO), OPEN LETTER FROM AN @IGNORED TEST, DEVELOPERS.ATLASSIAN.COM

40. People

41. CI is a practice, not a tool,
and requires discipline from the
development team.
“
”- CONTINUOUS DELIVERY (ADDISON-WESLEY), JEZ HUMBLE AND DAVID FARLEY

42. The Culture of Green
powered by

43. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
CONCLUSION
THE CD BATTLE, AT ATLASSIAN

44. Culture is what happens
when the founders are not around.

45. The Build Master

46. The Build Breaker

47. Red is the new green.

48. Give feedback to people,
so it’s fed-back.

51. 0quarantined tests
out of > 200k test

52. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
THE CD BATTLE, AT ATLASSIAN
CONCLUSION

53. CI is not enough.
”
“
- CONTINUOUS DELIVERY (ADDISON-WESLEY), JEB HUMBLE AND DAVID FARLEY

54. 
The non-CD syndrome

55. I cannot fix that bug…
I’m busy writing a new one.
“
”
- ME, OR YOU, OR ANY DEVELOPER AFFECTED BY THE LACK OF CD

56. A deployment pipeline
  

57. A deployment pipeline, at Atlassian
09:0009:00  dev  

58. 09:00
DEV STAGING PROD
A deployment pipeline, at Atlassian
 dev  

59.  dev  
09:00
10:00
A deployment pipeline, at Atlassian
 dev  

60.  dev  
 dev  09:00
10:00
DEV STAGING PROD
A deployment pipeline, at Atlassian

61. 09:00  dev  
 dev  
stg
09:00
10:00
16:00
A deployment pipeline, at Atlassian

62. 09:00  dev  
stg
 dev  
09:00
10:00
16:00
DEV STAGING PROD
A deployment pipeline, at Atlassian

63. 09:00  dev  
 dev  
09:00
10:00
16:00
16:15
stg
A deployment pipeline, at Atlassian

64. 
09:00  dev  
10:00  dev  
09:00
10:00
16:15
16:00 stg
16:30
A deployment pipeline, at Atlassian

65. 09:00  dev  
10:00  dev  
09:00
10:00
16:15
16:00 stg
16:30
10:00 prd
A deployment pipeline, at Atlassian


66. 
09:00  dev  
10:00  dev  
09:00
10:00
16:15
16:00 stg
16:30
10:00 
DEV STAGING PROD
prd
A deployment pipeline, at Atlassian

67. Free people to do
the interesting stuff,
and let Bamboo do the rest.

68. Wax in, wax off.

69. Agenda
CI ANATOMY
THE CI BATTLE, AT ATLASSIAN
CI CULTURE
CI INTRODUCTION
THE CD BATTLE, AT ATLASSIAN
CONCLUSION

70. 19
34
18
42

71. Do it, or do not.
There is no try. ”
“

72. Do it, or do not.
There is no try. ”
“

73. Do it,
with . ”
“

74. Thank you!
ESTHER ASENJO • BAMBOO DEV TEAM LEAD • ATLASSIAN • @STHREO