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
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