Continuous Integration Tools and HP ALM

Continuous Integration (CI) has become a popular implementation technique in today’s IT shops. More than ever before, organizations require the ability to integrate testing tools with delivery platforms in order to perform robust and timely testing for code builds.

To accommodate this demand HP’s Apps 12 platform (ALM/QC) provides integration with today’s most popular CI tools (such as Jenkins and Hudson). Additionally, other CI tool providers have created stable add-in products (such as AntHill Pro).

Because configuring the above-mentioned links can sometimes be challenging to an organization’s already strained resources, we at Citizencrane solutions offer training/assistance configuring ALM with the integration tool of your choice. This includes custom development services if needed.

Consider one possible integration architecture:

Common integration

Notice that in this architecture, integration between ALM and a CI tool revolves around the configuration of a middleware client(s). The client performs the duties of translating requests to/from the CI tool to ALM, and launches execution of a test on the execution host farm. This configuration is popular because it reduces the hosts that must be configured in the CI tool, yet allows execution on one or more execution hosts.

If your organization requires a more complex CI-to-ALM architecture please contact us directly, and we can work with your organization to build a platform that meets all of your needs!