One of Continuum's foundational principles is to provide a solution framework that doesn't require you to re-engineer any of the progress you've already made on your journey toward Continuous Delivery. We recognize and embrace the many tools and frameworks available that serve their target functionality very well, and therefore we choose to integrate rather than replace whenever and wherever possible.
Types of Integrations
Continuum is a suite of tools, and how we integrate with various other products depends on the features the target tool offers or the purpose it serves. VersionOne Continuum is extremely flexible and we integrate with various tools and platforms according to the nature of their functionality. Below is the list of integrations that Continuum supports, without going into the nitty-gritty of how or why.
For the sake of readability, the integrations are grouped into sections according to the general purpose of the tools themselves.
Continuum integrates with the following version control systems - specifically the ability to monitor repositories in these systems, detect when changes are committed, affiliate those changes with work items from supported planning tools, and initiate automation.
Affiliating actual developer work with the planning system is a central principle of Continuum. While the depth of feature integration varies for each of these systems, all of them support commit/work item affiliation.
Continuum recognizes all agile software delivery processes have already made an investment into a popular CI tool
SonarQube - find out more about this integration in the SonarQube integration page.
Continuum implements access to the following messaging services.
Continuum automation routines can natively make connections to and interact with the following data storage platforms.
Microsoft SQL Server
Continuum implements a full set of "command and control" features for the following virtualization technologies.
Amazon Web Services
Microsoft Azure (beta)
Continuum, by default, can easily interact with any host available on the network using standard protocols and no agents are required. The following interactive protocols are available:
All flavors of unix
Less Formal Integrations
In some cases, the nature of a popular tool may be such that a formalized integration isn't practical. For example, where Jenkins provides a server with an API to which you can issue a 'build' command, some popular deployment automation or testing tools do not have an official server with published methods. (For example, Cucumber tests are executed by running the test definition with a snippet of Ruby script, and while Puppet Enterprise provides an 'mco rpc' mechanism for invoking an action on a specific agent, it's still a command that must be issued.)
All of these tools fit perfectly into the fundamental design of Continuum Automate. Automate adds the missing link - allowing you to create complete test suites, deployment routines, etc - essentially encapsulating these fantastic tools into objects that can be stored and managed centrally and plugged in to higher level delivery pipelines.
Following are examples of these less formalized integrations, all of which are easily implemented in an Automate Task.
These are examples we commonly implement in Automate. Any tool that is scripted by nature is a good fit for Automate, so it's absence from this list by no means should suggest it isn't supported or can't be easily implemented.