Jenkins Software monitors executions of jobs that are repeated and currently Jenkins focuses on the following two jobs:
Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.
A Jenkins plug-in has been added that enables you to trigger a LoadRunner scenario as a build step, and present its results in the Jenkins Results dashboard.
Yes, LoadRunner 11.52 has a plugin available to work with Jenkins. The plugin is named: hp-application-automation-tools-plugin and can be found [http://wiki.jenkins-ci.org][1]. This site will contain a full download, documentation and support for this plug-in.
This plugin allows Jenkins to trigger HP tests such as: Test sets on Application Lifecycle Management, tests saved on the file system from Unified Functional Testing, QuickTest Professional, or Service Test, and LoadRunner scenarios.
This plugin currently supports the following HP Applications:
* HP Unified Functional Testing 11.50 (QuickTest Professional and Service Test 11.50 capabilities)
* HP Service Test 11.20 and 11.50
* HP LoadRunner 11.52
* HP QuickTest Professional 11.00
* HP Application Lifecycle Management 11.00 and 11.50
* HP ALM Lab Management 11.50
* HP Quality Center 10.00, with the QuickTest Professional Add-in for triggering test sets
If you are working with Quality Center 10.00 or earlier, and QuickTest Professional 9.x or 10.x, use the Quality Center Plugin.
[1]: http://wiki.jenkins-ci.org