The document outlines Continuous Integration (CI) as a software development practice that improves team collaboration by integrating work frequently, usually daily, and automating error detection through builds. It discusses the benefits of CI, including reduced risks, improved project visibility, and enhanced team confidence, while presenting Buildbot as a framework for implementing continuous integration. Additionally, it details Buildbot's architecture, configuration options, and offers tips for effective usage.

1. Buildbot
The Continuous Integration
Python framework

2. Steps
● Continuous Integration
○ Definition
○ Benefits
● Buildbot
○ Architecture
○ Views
○ Configuration
● Conclusions, tips, Q&A, ...

3. Who am I?

4. CI: Definition by Martin Fowler
Continuous Integration is a software development
practice where members of a team integrate their
work frequently, usually each person integrates at
least daily - leading to multiple integrations per day.
Each integration is verified by an automated build
(including test) to detect integration errors as
quickly as possible. Many teams find that this
approach leads to significantly reduced integration
problems and allows a team to develop cohesive
software more rapidly.
http://goo.gl/FC9S4U 1/3

5. CI: Benefits
● Reduce risk and time.
● Reduce manual repetitive processes.
● Create a version of software by a known,
reliable, proven and repeatable process
versioning.
● Improve visibility of project status.
● Achieve greater self-confidence and
security in the development team.
2/3

6. CI: Why? How?
● Process quality.
● Product quality.
● People quality.
3/3

7. Buildbot: System Architecture
1/2
BUILDSLAVES
CHANGES = CHANGESOURCES
SCHEDULERS
COMMANDS = BUILDERS
FACTORY = STEPS
STATUS TARGETS

8. Buildbot: Buildmaster Architecture
2/2

9. View: Waterfall
1/3

10. View: Build Slaves
2/3

11. View: Console
3/3

12. Config: HTML Templates = Jinja2
1/7

13. Config: PROJECT IDENTITY + DB
URL
2/7
SQLite
MySQL
PostgreSQL

14. Config: BUILDSLAVES
3/7

15. Config: CHANGESOURCES
4/7

16. Config: SCHEDULERS
SingleBranchScheduler
AnyBranchScheduler
Dependent Scheduler
Periodic Scheduler
Nightly Scheduler
Try Schedulers
Triggerable Scheduler
NightlyTriggerable Scheduler
ForceScheduler Scheduler 5/7

17. Config: BUILDERS
ShellCommand
BuildEPYDoc
Sphinx
PyFlakes
PyLint
FileExists
CopyDirectory
RemoveDirectory
MakeDirectory 6/7

18. Config: STATUS TARGETS
WebStatus
MailNotifier
IRC Bot
StatusPush (to callback)
HttpStatusPush (in json)
GerritStatusPush
GitHubStatus 7/7

19. Conclusions, tips, Q&A, ...
● Display = Collaboration
● Python framework
● X branches * Y schedulers * Z status * N slaves
● A starting point: http://goo.gl/AcKoGZ
(https://github.com/carlessanagustin/buildbot-bootstrap)

20. Thank you very much
@carlesanagustin
___@carlessanagustin.___
www.carlessanagustin.com
+34 655 4XX XXX