The VersionOne Platform SDK simplifies and streamlines the process of integrating with external systems, such as a test automation tool, bug tracker, or code management solution. To assist teams in implementing custom solutions, VersionOne has open-sourced a series of integrations with some popular tools. These integrations are reference implementations that teams can use and extend to meet their own unique requirements.
The following image outlines the overall platform architecture and examples of VersionOne’s open-source integration components.
The integration we provide fall into two main categories:
- Applications provide a user interface for viewing, adding, or modifying data within VersionOne
- Services perform background operations integration and require no human interaction
All of these applications are built on the SDK or the Legacy APIClient libraries.
Reference Implementations
The reference implementations are summarized below. For a more complete description, including installation instructions, visit the home page for the implementation.
VersionOne's Visual Studio Add-In (VSAddin) provides direct interaction with VersionOne developer tasks from within Visual Studio. This enables Microsoft platform developers to update VersionOne task status, estimates, remaining effort, etc., without needing to leave the comfortable confines of the Visual Studio IDE.
The VersionOne Eclipse Plugin (V1EclipsePlugIn) provides direct interaction with development task in VersionOne within the Eclipse IDE. This enables Java developers to update VersionOne task status, estimates, remaining effort, etc., without leaving the confines of the Eclipse environment.
The VersionOne Requestor allows stakeholders across your organization to submit requests to your VersionOne projects. This standalone web application is a simple way for any user to submit a request for a new feature or report a defect without having access to the full VersionOne application or knowledge of your VersionOne project structure.
VersionOne CruiseControl.NET Publisher
The VersionOne CruiseControl.NET publisher creates a record of CruiseControl.NET builds in VersionOne, so the development teams can quickly view builds associated with a story or defects. This visibility is useful when identifying what build to use for verification or when generating release notes.
VersionOne's integration with Microsoft Team Foundation Server (V1TFS) provides your organization with visibility into change while freeing the development team to focus on deliverables. This is accomplished by associating TFS builds and changesets with workitems in VersionOne. This visibility can be useful when tracking down defects or performing code reviews. It can also help with selecting a build to release or generating release notes. The TFS Check-in policy ensures that each check-in contains the information necessary to make this association.
The VersionOne Subversion Integration (V1Svn) creates a record of Subversion changesets in VersionOne, so the development team can quickly view all of the code changes for a story or defect. This visibility can be useful when tracking down defects or performing code reviews.
The VersionOne Perforce Integration (V1Perforce) creates a record of Perforce changesets in VersionOne, so the development team can quickly view all of the code changes for a story or defect. This visibility can be useful when tracking down defects or performing code reviews.
The VersionOne JIRA Integration (V1JIRA) creates defects in VersionOne based on issues in JIRA. Using this integration your organization can manage and triage issues reported by customers and promote them to VersionOne once you determine a fix is necessary.
The VersionOne Bugzilla Integration (V1Bugzilla) creates defects in VersionOne based on bugs in Bugzilla. Using this integration your organization can manage and triage bugs reported by customers and promote them to VersionOne once you determine a fix is necessary.
The VersionOne HP Quality Center Integration (V1QualityCenter) provides a two-way flow of information, allowing an organization to leverage its investment in HP Quality Center as part of an integrated platform for agile development. This integration will send tests from VersionOne to Quality Center and update test pass/fail results from Quality Center to VersionOne. When new defects are created in Quality Center, it will also send those defects to VersionOne and update Quality Center once the defect is fixed in VersionOne.
The VersionOne HP Quick Test Professional Integration (V1QuickTestPro) imports the results of tests defined HP's Quick Test Professional (QTP) into VersionOne. The results of an individual QTP test can be linked to a Test Artifact in VersionOne, so that development, and you organization, will receive quick feedback on which tests are passing and failing.
The VersionOne FitNesse Integration (V1Fit) imports FitNesse test results into VersionOne, making the latest test results more visible across the an organization. The results can be recorded at two different levels of granularity—project and test. The aggregate results for a suite of tests in FitNesse can be linked to a project in VersionOne, so that everyone can see the health of their project from a testing standpoint from within VersionOne. The results of an individual FitNesse acceptance test can be linked to a Test in VersionOne, so that development team members receive quick feedback on which tests are passing and failing.
The VersionOne.ServiceHost.exe (ServiceHost) is an application framework that can be installed and run as a console application or as a Windows Service. It provides a host process and shared services (e.g. publish/subscribe event engine, logging, persistence) to any number of 'hosted services'. At startup, the ServiceHost initializes all configured hosted services specified in the configuration file. This framework is used as the foundation for the above integrations, except HP Quick Test Pro.
