The integration between Jenkins and TestLink can be achieved with Jenkins TestLink Plug-in. The plug-in resides in Jenkins, being able to use some of its nice features like executing multiple jobs, scheduling jobs, distributed execution and a plethora of plug-ins. To retrieve the data from TestLink for tests, as well as to report the test case execution status to TestLink, the plug-in uses TestLink XML-RPC API.
This way, while Jenkins handles the execution of jobs and tasks such as downloading source code from an SCM, TestLink maintains the structure of your tests, as well as other assets as Test Plan, Custom Fields, Reports and Baselines.
We will see how to configure our envinronment for this integration throughout the next chapters. While it is good to have a good written explanation on how this integration works, probably it is a lot easier to understand how it works with a hands-on. The rest of this guide explains how to configure Jenkins and TestLink to run automated tests from a sample test project. This test project is a Java project that uses Maven and TestNG and you can download the source code from https://github.com/kinow/jenkins-testlink-plugin-tutorial (as well as the DocBook source for this book).
The current version of Jenkins TestLink Plug-in while this book is being written is 3.0.2.
Jenkins TestLink Plug-in is licensed under the MIT License and its code is stored in github - http://github.com/jenkinsci/testlink-plugin.