Continuous integration (CI) is the practice, in software engineering, of merging all developer workspaces with a shared mainline several times a day. It was first named and proposed as part of extreme programming (XP). Its main aim is to prevent integration problems, referred to as "integration hell" in early descriptions of XP. CI can be seen as an intensification of practices of periodic integration advocated by earlier published methods of incremental and iterative software development, such as the Booch method. CI isn't universally accepted as an improvement over frequent integration by supporters of the latter. It is important to distinguish between the two forms as there is disagreement about the virtues of each.
There are many CI solutions, but Jenkins is one of most popular one.
Jenkins is an open source continuous integration tool written in Java. The project was forked from Hudson after a dispute with Oracle, which claims the right to trademark the Hudson name and has applied for such a trademark as of December 2010.
Jenkins provides continuous integration services for software development. It is a server-based system running in a servlet container such as Apache Tomcat. It supports SCM tools including CVS, Subversion, Git, Mercurial, Perforce and Clearcase, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands. The primary developer of Jenkins is Kohsuke Kawaguchi. Released under the MIT License, Jenkins is free software.
Builds can be started by various means, including being triggered by commit in a version control system, scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build URL.
More information on Jenkins see on http://jenkins-ci.org/
Check if Jenkins service installed as a service. If it is not, follow this tutorial
By default, every Windows service runs from SYSTEM account which have not needed build environment.
So you should modify service settings to run it with regular user account which have Delphi and OwlyCI installed. Right-click "My computer" on Desktop, then "Manage", then "Services", right-click on Jenkins and edit properties ("Log on" tab). Choose your regular user name and enter its password.
Restart Jenkins service.
You can check result by adding such easy Jenkins job:
If all correct it will show your user name
Now add new Jenkins job, and make following settings:
"c:\Program Files (x86)\OwlyCI\owlyci.exe" --build owlyci.xml
Please check full path to your OwlyCI installation.
which means compiled .exe of our project
That's all. Easy, right ?
Now we can test how CI works by click on "Build now"