Policy-Based VCS Connectors

CA Technologies has a policy-based VCS connector that supports the following Version Control System products:

The policy-based VCS Connector allows you to cover multiple repositories in one configuration file. Repositories can be specifically mentioned in a list or can be specified using shell-like regex/wildcard characters (for example, foo*, test-*-alpha). In addition to posting Changeset information to CA Agile Central, you can configure the connector to:

  • Scan for and post related Pull Request information
  • Map a VCS user name to an Agile Central username that will display as the Changeset Author in Agile Central
  • Trigger a State change to a mentioned artifact based on information in the commit message

The policy-based VCS connect (PBVCS) is a one-way/one-time mechanism. Information in your VCS is never altered, it is consulted for commit/pull-request information and important aspects of those are reflected in the CA Agile Central system for your subscription in appropriate Changeset/PullRequest items. The connector is installed and runs on your platform according to your scheduling.

Bitbucket (BB)

The VCS Connector for Bitbucket (BB) comprises code that skims the Bitbucket system for recent commits and extracts information from the commit messages and posts changeset information to a CA Agile Central SCMRepository according to specifications in a configuration file. This connector supports both Bitbucket Server and Bitbucket Cloud.

You can include FormattedIDs (for example: US42) in commit messages. The connector processes all commits for configured repositories and pushes information about those commits into changeset objects in CA Agile Central. If a valid FormattedID is found in a commit message, the changeset created by the connector is associated with that defect, story, or task in CA Agile Central.

Supported versions: 5.0, 5.1, 5.2

See the Bitbucket Installation & User Guide for information on installing, configuring, and using the connector.

GitHub

GitHub is a web-based hosting service for software development projects that use the Git version control system. GitHub offers both commercial plans and free accounts for open source projects. GitHub is the most popular Git-hosting site, and the most popular open-source hosting site.

CA Agile Central's GitHub Integrations will:

  • Create changeset information

    Associated with the workspace and SCMRepository you define for a given GitHub repository, it will create changeset and change information in CA Agile Central. When viewing an artifact in CA Agile Central, there are details about changesets associated with commits from GitHub push activities. CA Agile Central also provides reports that use the artifact, changeset, and change information to provide insight into which files get changed more frequently or that are associated with higher than normal defect rates and other useful reports.

  • Associate changeset to artifacts

    The commit messages are scanned for a FormattedID of a CA Agile Central artifact, and if found, the artifact is associated to the changeset created in CA Agile Central.

See the CA Agile Central VCS Connector for GitHub for information on installing, configuring, and using the integrations.

Supported version: 1.1

GitHub Enterprise

GitHub Enterprise is the self-hosted equivalent of GitHub. Organizations that are unable to have their materials in the cloud use this approach to gain the benefits of the GitHub approach and technology. The are minor differences in a VCS Connector configuration file when using GitHub Enterprise as compared with GitHub. Otherwise, the connector operates in a similar manner as described for GitHub.

See the CA Agile Central VCS Connector for GitHub for information on installing, configuring, and using the integrations.

Microsoft VSTS/TFS 2017

The CA Agile Central VCS Connectors for VSTS and TFS 2017 posts information about VSTS and TFS 2017 repository commits to CA Agile Central, relating those commits to CA Agile Central changesets and artifacts if sufficient information is contained in the VCS commit messages to identify the relevant artifacts. The connector will also update the state of relevant CA Agile Central artifacts, specifically defect state or user story schedule state when commit messages contain appropriate syntax, for example US123 In-Progress. The CA Agile Central VCS Connectors for VSTS and TFS 2017 are classified as a one-way and one-time mechanism. Information in VSTS and TFS 2017 is never altered; information is only written in Agile Central and no duplication of data is attempted or allowed.

The Agile Central VCS Connector as of version 2.0.0 includes functionality that detects the creation of VSTS and TFS 2017 pull request items and posts corresponding pull request items in Agile Central when the configuration option for this is present in the target configuration file.

The Agile Central VCS Connectors for VSTS and TFS 2017 consists of software that you run on your platform according to your desired schedule. The configuration of the connector is policy-based, meaning that you do not need to provide a separate configuration file for each VSTS repository for which you want the connector to operate. The policy-based nature allows you to scope to all or a subset of repositories within a VSTS or TFS 2017 project.

See the VCS Connector for VSTS/TFS 2017 installation guide for information on installing, configuring, and using the connector.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.