Continuous Integration Tool Jenkins Continuous Integration Tool By: Donatas Kurapkis 2016 Vilnius

Agenda Continuous Integration (CI) Jenkins Conclusion Benefits? What is it? Basic example Why jenkins? Automation example Demo Conclusion

Continuous Integration (CI) “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” – Martin Fowler

Continuous Integration (CI) So it means that the system is: Integrated; Built; Tested; Archived; Deployed;

CI - Benefits? Immediate bug detection No integration step in the lifecycle A deployable system at any given point Record of evolution of the project

Jenkins Branched from Hudson Java Based Runs in servlet container Tomcat, Glassfish Has many plugins Testin, Notifications, Reporting, Triggers and etc. Since 2005 http://jenkins-ci.org

What is it ? Jenkins - is continuous integration tool allowing to integrate different stuff into one automated system, for example release automation, or tests automation.

Basic example

Why Jenkins? Easy to configure Easy to install Have many plugins Integration with popurial open source repositories like GitHub Ability to run commands Multithreading By combining Jenkins with Ant, Gradle, or other Build Automation tools, the possibilities are limitless It’s free

Automation example

DEMO

Conclusion Perfect tool for automations tasks; Free; Do not limits your capabillities;