Continuous integration and delivery using Atlassian Bamboo allows for: 1) Splitting build and deployment projects to support multiple environments with Bamboo plans, stages, jobs, and tasks organizing the build pipeline. 2) Releasing any version through deployment projects at the push of a button by ensuring every change is releasable. 3) Integrating Bamboo with other Atlassian tools like Jira and Bitbucket for tracking issues and source code.

1. Continuous Integration using
Atlassian Bamboo
CONTENT
Continuous Integration & Continuous Delivery
Teamcity vs Bamboo
Bamboo overview: Plans, Stages, Jobs, Tasks
Bamboo agents
Branches & Merging
CD in Bamboo: Deployment Plans, Releases
BGD projects example
Integration with Jira and Bitbucket

2. CONTINUOUS INTEGRATION
1
CONTINUOUS INTEGRATION
=
EARLY ′′ FAIL FAST ′′ FEEDBACK
Developers
Source
Repository
Compile
Run unit tests
Run
integration tests
Package
Build
process
Code
commits
Triggers
build

3. CONTINUOUS DELIVERY
2
Developers
Source
Repository
Code
commits
Compile
Run unit tests
Run
integration tests
Package
Build process
Web Server
Deploys
application
CONTINUOUS DELIVERY
Continuous Delivery is the natural
extension of Continuous Integration:
an approach in which teams ensure
that every change to the system is
releasable, and that we can release
any version at the push of a button.

4. TeamCity
3
BGD PROJECTS

5. TeamCity
4
PROBLEMS
A LOT OF PROJECTS
x = (project for build + project for deployment) * environments
1
HOW TO IDENTIFY WHAT IS DEPLOYED?2
NO EASY WAYS TO INTEGRATE WITH JIRA3
HARD TO MAINTAIN4

6. Bamboo
5
REASONS
A LOT OF PROJECTS
BUILD AND DEPLOYMENT PROJECTS ARE SPLITTED1
HOW TO IDENTIFY WHAT IS DEPLOYED?
DASHBOARDS FOR BUILD AND DEPLOYMENT PROJECTS2
NO EASY WAYS TO INTEGRATE WITH JIRA
GOOD INTEGRATION WITH ATLASSIAN STACK3
HARD TO MAINTAIN
LACK OF PLUGINS, BUT EVERYTHING CAN BE DONE WITH POWERSHELL4

7. Bamboo
6
REASONS

8. Bamboo
7
PLAN
STAGE STAGE
JOB
TASK
TASK
TASK
JOB
JOB
TASK
TASK
TASK
JOB
JOB
TASK
STAGE
TASK
TASK
BUILD PROJECT
STRUCTURE

9. Bamboo
8
TASKS = BUILD STEPS

10. Bamboo
9
ORDERED EXECUTION
OF TASKS
SIMULTANEOUSLY
EXECUTION
● UI build tasks
● Backend build tasks
JOBS
=
CONTAINERS FOR TASKS

11. Bamboo
10
SIMULTANEOUSLY
EXECUTION OF JOBS
ALL JOBS IN CURRENT
STAGE MUST COMPLETED
SUCCESSFULLY BEFORE
MOVING TO THE NEXT STAGE
STAGES
=
CONTAINERS FOR JOBS

12. Bamboo
11
PLANS
=
CONTAINERS FOR STAGES
● Can be triggered (for example, by changes to source control)
PLAN ORGANIZES WHOLE BUILD PIPELINE,
VARIABLES, PERMISSIONS, NOTIFICATIONS,
.. TRIGGERS

13. Bamboo
12
BUILD PLAN ARTIFACTS
CAN BE SHARED BETWEEN
● Jobs
● Build Plans
● Build Plans to
deployment projects

14. Bamboo
15
AGENTS
Plan ACME
Build no.
ACME-123
Build ACME
Network
Capability requirements
Builder = Maven
JDK = 1.5
Custom: fast build = true
Shared local capabilities
Builder = Ant
JDK = 1.5
Shared local capabilities
Builder = Maven
JDK = 1.4
Agent-specific capabilities
JDK = 1.5
Custom: fast build = true
Remote Agent 2
Remote Agent 3
Remote Agent 1
BAMBOO SERVER
Local Agent 1
Local Agent 2
Plan ACME submits
build number 123
to the Build Queue
The Build Queue forwards build n.o. ACME-123
to the next available agent whose capabilities
meet Plan ACME’s requirements.
(Note: agent-specific capabilities
override shared capabilities)
An agent can run a job if its
capabilities match the
requirements of a job:
an executable (e.g. Node Js)
a JDK
a Version Control System
client application (e.g. Git)
a custom capability. This is a
key-value property which
defines a particular
characteristic of an agent

15. Bamboo
16
DEDICATED AGENTS

16. BRANCHES
17
CONFIGURATIONS

17. BRANCHES
18
DASHBOARD

18. MERGING
19
CONFIGURATIONS

19. MERGING
20
FAILS

20. Bamboo
13
RELEASES
Release is a snapshot of any number
of artifacts that will be used in the
deployment process and their
associated metadata, such as
JIRA issues, code changes and any
test metadata
A release is created from the result
of a single build

21. Bamboo
14
RELEASES

22. Bamboo
21
DEPLOYMENT PROJECTS

23. BGD PROJECTS
22
BRANCHING MODEL
Master Develop
Feature
B
A
C
K
E
N
D
MasterDevelop
Dev environment
Feature
Release-tag Release-tag
F
R
O
N
T
E
N
D

24. INTEGRATION
23
WITH JIRA

25. INTEGRATION
24
WITH JIRA

26. INTEGRATION
25
WITH BITBUCKET

27. INTEGRATION
26
DEMO
WITH BITBUCKET & JIRA

28. Bamboo
27
DEMO
HINTS
Tasks sharing
Rollback
Hot fixes