CA Agile Central VCS Connector for Subversion Installation & User Guide

Connector downloads:

To download the connector, follow the steps here.

Note: This documentation applies to the latest polling method version of the Subversion connector.

The Subversion to CA Agile Central Connector helps you show traceability of code changes to artifacts in CA Agile Central.

The Subversion to CA Agile Central connector comprises code that skims a centralized master Subversion repository for recent commits. It extracts information from the commit messages, and posts changeset / change information to a CA Agile Central SCMRepository, according to specifications in a configuration file. While it is possible to have the connector installed on only one computer for your company, you can also choose to install the connector on multiple computers depending on how your organization is structured and the number of repositories that need to be reflected in CA Agile Central.

When developers put FormattedIDs, for example US42, in their commit messages, the connector processes all commits for configured repositories and pushes information about those commits into changeset objects and change 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.

Example:

"Fixed DE1987 by changing preamble paragraph 3"

If Rally defect DE1987 had a state of Open prior to the commit and run of the connector, then subsequent to the operation of the connector processing this particular changeset, the state of Rally defect DE1987 would display as Fixed. Please note this message is case-sensitive, fixed is not the same as Fixed. The yml file will need UpdateArtifactState value set to True to process a state change.

The commit message may contain references to more than one artifact. For example, this is known to work:

"Test commit msg with multiple artifacts Fixed DE9 Closed DE8"

A typical workflow would be for one of your team members to be assigned DE42 in CA Agile Central. When they make a code change and commit it. They would include text in the commit message like "Found an issue with line breaks - fixed DE42". When the connector runs again, it locates that commit message and links the information about the commit to CA Agile Central defect DE42.

This installation guide includes the following:

Prerequisites

  • Ruby 2.2.6  -  This is the supported version.

    The connector may not be compatible with Ruby 2.3.x and 2.4.x, we have not certified this connector with those versions, only 2.2.6 is certified. You may want to investigate how to use the Ruby version manager software (rvm) that makes installation and use of specific versions of Ruby simpler.

  • Ruby Development Kit for Ruby 2.0 to 2.3 (** Windows only **)
    1. Download the DevKit-mingw64-64-4.7.2-20130224-1432-sfx.exe from here.
    2. Add path to the devkit’s bin directory to environment Path variable.
    3. cd to the Ruby DevKit root directory.
    4. run command: ruby dk.rb init
    5. run command: ruby dk.rb install
  • Choose a machine which will be used to run the connector
  • If the connector machine is a different machine than the Subversion server, note the Subversion server's address and name
  • Gather the paths to the centralized master repositories from which you will gather information
  • Select the Rally workspace into which the changeset/change information will be posted

Supported platforms

The connector supports running in a variety of platforms. This software is written in Ruby and has been tested and certified using Ruby 2.2.6. Subsequent to June 27, 2018, it will not work with any earlier version of Ruby. We expect the connector to work with subsequent stable versions of Ruby. If this software is for use on a Linux, Unix, or MacOSX system, it must be installed subsequent to installing the http client and rally_api gems.

You can run the connector in one of two ways:

  • In Windows as a packaged executable (recommended if you want the connector to run on a Windows machine)
  • In any OS through Ruby as a packaged gem (on any OS with Ruby 2.2.6 or greater installed)

Set up CA Agile Central

Note: We strongly recommend creating the connector user with Workspace Administrator permissions. This will allow the connector user access to any new projects that may be added to the Workspace in the future (A user with Editor permisssions only will not automatically be added to new projects). If the Connector User does not have access to projects, changesets will be created in the SCM Repository only and will be orphaned (not attached to any artifacts).

Verify that your target WorkspaceConfiguration object has BuildandChangsetEnabled set to true.

Your CA Agile Central workspace administrator needs to enable this for your target workspace. If it is not enabled, the connector will work, but you will not be able to see any of the changeset/change information that is associated with your Rally work items (story, defect, task).

The workspace administrator must edit the workspace and do the following:

  1. Click the Setup icon .
  2. Click the Workspaces & Projects tab.
  3. On the Workspaces & Projects summary page, select your workspace.
  4. From the Actions drop-down, select Edit.
  5. On the workspace editor, select the checkbox labeled Enable Build and changeset.
  6. Click Save & Close.

Set up the connector

The Subversion connector is controlled by three different files:

Repository configuration file

For each Subversion repository that you want to have reflected in CA Agile Central, you will need a connector configuration file which will be located in the configs subdirectory of the connector software you just installed.

This configuration file must be in YAML format. A connector configuration file contains information on how the connector operates in terms of how to interact with CA Agile Central and the identity and location of the Subversion repository. There is an example configuration file shipped with the product named configs/sample.yml. Make a copy of it and use it for your repository. We suggest naming your YAML configuration file similar to your repository name. For example, if your repository name is My-Svn-Repo, then name your YAML configuration file My-Svn-Repo.yml (for simplicity). Edit your new repository configuration file and modify the values to fit your environment.

Warnings about YAML syntax:

  • The tab character is not a valid YAML character.
  • Enclose special characters in quotes, such as if the password has exclamation marks ("!") or hashes ("#").
  • The comment character ("#") must be separated from any previous element by at least one space. For example, this string: ".../dir/dir2#this is a comment" is invalid.

RepositoryName

The conventional practice is to name the CA Agile Central RepositoryName the same as your Subversion repository. The value you provide as the RepositoryName value is given to an SCMRepository instance in CA Agile Central. The CA Agile Central RepositoryName can be different from the Subversion repository name, if so desired. Within the Rally section of your YAML configuration file, the value for RepositoryName is the name of the Rally SCMRepository to which changeset/change items will be associated. If this SCMRepository container does not exist, the connector will create it in the user's target workspace.

Lookback

There is an optional Lookback variable which can display on either or both of the Rally and Subversion sections. By default, the value for this parameter is assumed to be in minutes. You may use other units of time by specifying a suffix character of m (minutes), h (hours), or d (days).

Examples:

Lookback: 90
Lookback: 120 m
Lookback: 8 h
Lookback: 10 d

If you do not explicitly provide a Lookback value, the connector uses a default value of one hour. If you do specify a Lookback value in one section, we highly recommend specifying the value for it in the other section. If the Lookback values are not identical in the two sections, there is the possibility that a changeset from Subversion would not be reflected in Rally.

RepositoryBase

Within the Subversion section of the configuration file, use the RepositoryBase to specify full pathname of the centralized master Subversion repository (not the working copy of the repository).

Example repository configuration file

---
     
VCSConnector:
     
Rally:
    Server              : rally1.rallydev.com           #
    Protocol            : https                         #
    Username            : jojo@muchly.com               #
    Password            : 22333four                     # (this will be encoded after first use)
#   APIKey              : hgiotewhgeiwhgh325930503453490    # can be used in place of Username / Password entries
    Workspace           : VanillaBean                   #
    RepositoryName      : Balloon                       # If it doesn't exist, it'll be created
#   Proxy               : some_proxy.yoursite.com:9876  # or an IP address:port
#   ProxyUser           : outbound                      #
#   ProxyPassword       : bvc-357%GNQ                   #
    Lookback            : 90                            # minutes by default, use h/d suffix for hours/days
    UpdateArtifactState : False                         #
    StateExtractorClass : BasicActionsAndArtifactsExtractor(message) # Only used if above is True
    Debug               : False                         # True for debug output
     
Subversion:
#   Server              : svnsvr.company.com            # specified if repo is not local
    RepositoryBase      : /home/svn/repos/bigproject    # Complete pathname to the centralized-master Subversion repository
    Lookback            : 90                            # minutes (defaults to 120)
    MaxItems            : 100                           # Max number of items to process per run
#   RevURI              : http://svnserver.com/repo/{revnumber}?id={revnumber} # if running web access to repo
#   FileURI             : http://svnserver.com/repo/{filepath}?id={revnumber}  # if running web access
    Debug               : False                         # Set to True for additional debug output
     
Services:
    Preview             : False                         # When True, only show what would happen
    LogLevel            : Debug                         # Default value Info
#   PostBatchExtension  : MetricsPoster                 # For future use
     
Transform:
    Author              : Passthru                      # The default
#   Author              : EmailAddressAsRallyUser
#   Author              : FileBasedUserNameLookup(user_map.txt,":")
#   Author              : RallyUserNameLookup(FirstName,LastName)
#   Author              : UserLookupChainGang(FirstName,LastName,user_map.txt,":")
#   Author              : UserNameDomainAugmentLookup(MyDomain.com)
     
...
  • URIs
    The RevURI and FileURI (in the Subversion section) are meant to be the root URI if you are using a web front end for your system. The URI will be used as a base for the link to the changesets and files from within the Rally Changeset. For example, if you have http://server:port/Subversion/rev/ as your root URI for your web access to Subversion (like Apache or ViewVC or WebSVN or VisualSVN), a link will be made in Rally for the changeset to http://server:port/Subversion/rev/12345 for changset 12345. The strings {revnumber} and {filepath} will be substituted in when the connector builds the link stored in Rally.
  • Proxy
    The three Proxy items are commented out by using a # in front of the item. Within a YAML file, any line beginning with a # character is ignored and any content following a # character sequence is ignored (including the  # sequence).

  • *** NOTE: The term root URI as discussed here is _not_ synonymous with the RepositoryBase value. The repository base MUST be a valid filesytem path on the host for the Subversion repository. A root URI is configured specific to the web server you are running and how that has configured routes to resources.

User mapping file

The file configs/user_map.txt determines how user names are translated between your Subversion system and your CA Agile Central subscription. If the user names are universally identical in both systems, then you can either comment out all Author sub-items underneath the Transforms section or you can set the value for the Author field in the Transforms section to Passthru. If there is a deterministic mapping that can transform a Subversion user name to a CA Agile Central user name, you will need to adjust the transformation value for Author to the appropriate classname. Consult the User-Mapping-Strategies text document (part of the installation) to determine which technique fits your needs.

Once you identify a suitable Author transformation technique, you'll need to modify the configuration file (in the configs subdirectory) to identify the Ruby class name that will implement that transformation. The Ruby class name must exist in a file of Ruby source code that is in a file in the plugin subdirectory.

Example user_map.txt file:
# Subversion repo username   CA Agile Central username
# ------------------------ : -----------------------
jpkole                     : test@rallydev.com
linuxuser1                 : tester1@rallydev.com
linuxuser2                 : tester2@rallydev.com
David Beckham              : love2bendit@fifacup.com
Yogi Berra                 : aphorisms@yankees.com

Repository time file

Each time the connector finishes running, it updates a repository time file in the base installation directory, which has a name like My-Svn-Repo_time.file. This file contains the date of the last Subversion commit processed by the connector. Therefore, when the connector runs again, it can locate where (such as, at what time in the past) to begin processing commits made by the user.

On the first invocation of the connector there is no time file, so the connector will look back 72 hours in to the past for commits.

You can edit this file and set the time to a value you prefer. For instance, if you have 50,000 check-ins that were performed over the previous five years, you may not want all of that past history reflected in CA Agile Central. If so, edit the time file and enter a date of a more recent starting point.

The file contains only one line: a time stamp in GMT/UTC time. The general format of the file is YYYY-mm-dd HH:MM:SS Z (where the Z is for Zulu or GMT/UTC time). The following are the contents of a typical time file:

2013-05-17 18:49:22 Z

Mapping SCMRepositories to VCS repositories

The VCS Connector was designed to operate where this is a one-to-one relationship between a CA Agile Central SCMRepository and a VCS repository (Git, GitHub, Subversion, Mercurial, and so on). When run, the VCS Connector creates a CA Agile Central SCMRepository item for the value specific in the connector config file if it does not already exist. This removes a small amount of administrative burden in that you do not have to create the CA Agile Central SCMRepository item before you run a configuration mentioning a new repository. A one-to-many mapping can create performance issues.

For each repository, there is a config file and a timefile. The timefile records the timestamp of the second-to-last commit for the repository. For example, you have an Apricot repository that had some flurry of commits last fall but nothing since and you also have a Banana repository that has had activity with the last couple of months. When commits for these two repositories get poured into a single Rally SCMRepository, it has the following effect. When processing the config for the Apricot repository, it is searching for recent Changeset records in Rally where recent is defined as the value in the timefile for Apricot. Since the last commit to that repository was last fall, there is going to be an excessive amount of information read-out of the single SCMRepository (because it is looking at all Changesets since last fall, not just the ones for Apricot).

Create a CA Agile Central API key

A CA Agile Central API Key can be created to use to access your subscription data without using your username and password.

To use the API Key in a connector, edit the Rally section in the config .yml file and add an APIKey line. When the APIKey configuration entry is specified, omit the Username and Password from the Rally config section. If an APIKey entry is present, the username and password are not used and a warning will appear in the log file if they are included in the config file. This is true even if the APIKey entry value is invalid, blank, or nil. If your subscription administrator has configured your subscription to be SSO only, you no longer need to add the user associated with the given APIKey value to the whitelist of authorized users.

The connector now uses rally_api version 1.2.1. Please note that the APIKey specified must have full access, a read-only api key will not allow the connector to write to CA Agile Central.

For help creating a full-access API Key, please visit http://help.rallydev.com/rally-application-manager.

Install the connector

Download the connector:

Subversion server versus use of ssh

The primary use case is for this connector to be run on the platform that the Subversion software and centralized master repository reside on. While it is possible to run this connector on a platform that is not the Subversion platform, that use case assumes the use of ssh and the proper setup of public and private key information. Setting up ssh and key files is beyond the scope of this document; consult the internet for information regarding ssh and PKI.

If you intend to use ssh when running the connector, it will be helpful to demonstrate that your key setup and permissions are correctly set independently of the connector. As the user who will be running the connector, in a shell running in a terminal window attempt the following:

$ ssh connector_user@svn_server_host  # substitute your actual user name and hostname...
$ ls -l

If this command runs correctly you'll get a long-format directory listing of the home directory for the connecter_user on the svn_server_host. If it does not run and provide that output, you'll need to troubleshoot common environmental error conditions such as non-availability of a private key file or improper directory/file permissions or target host setup for ssh connections. Only proceed towards running this connector when this command example succeeds for you.

Once you've demonstrated basic ssh usage using a key (so that you don't get challenged to provide a password) you can move on to establishing that you have a valid RepositoryBase value and that your Subversion installation allows the specific command necessary for the connector to run properly. In the following example, the RepositoryBase value is /opt/svn/repos/tech-project. Using ssh, attempt to run an svn log command on your Subversion host, substituting values appropriate for your environment.

$ repo='file:///opt/svn/repos/tech-project'
$ ssh -i $HOME/.ssh_keys/my_key_file_rsa  connector@svn_server_host svn log $repo

If this command succeeds, you can proceed with setup, configuration and running of the connector. Otherwise, you must identify and correct environmental factors (no key file, invalid user, etc.) before proceeding with attempting to operate the connector.

Installer versus operator file system permissions

As this connector is intended to run on an ongoing basis initiated by either cron or Windows Task Scheduler (WTS), it is important to consider the identity of the user who installs the connector versus the identity of the user when run through cron/WTS with regard to the permissioning and ACL of the directories and files in the connector installation. The runner of the connector must be able to read all files and must be able to write in the configs and logs subdirectories.

Distribution contents

1715 May 23 13:01 LICENSE
18419 May 23 13:01 README
4811 May 23 13:02 User-Mapping-Strategies
170 May 23 15:43 configs
136 May 23 13:02 extension
170 May 23 13:02 gems
1897 May 23 13:02 git2ca_agile_central.rb
2115 May 23 13:02 install_gems.rb
102 May 23 13:02 lib
136 May 23 15:36 logs
374 May 23 13:02 plugin
43520 May 23 13:02 vcseif-1.6.0.gem  

Installation

  1. Unzip the git2ca_agile_central-(version)-master-(build_number).zip file into a suitable directory where you want the software installed.
  2. Set environment variable GEM_COMMAND to gem executable located in Ruby installation directory. The location examples on Linux and Windows respectively are:
    • /myhome/.rvm/rubies/ruby-2.2.6/bin/gem
    • C:\Ruby226\bin\gem
  3. Run the install_gems.rb Ruby script to get all associated gems installed. If you see output similar to You don't have write permissions ... then you will need to either consult with your system administrator to obtain the necessary permissions (typically done by using sudo or other similar software) or have the system administrator run the install_gems.rb command. To run the command, in a console/terminal window at the prompt, type the following: ruby install_gems.rb

Run the connector

Preview mode

Within the Services section of your configuration file (configs/repo_one.yml, for example), is an entry for Preview. If not present, the default is False. When set to True, the connector does not modify any data in CA Agile Central, but rather ensures it can successfully connect to CA Agile Central with the credentials and information you have provided, as well as validating the use of the use of the svn command. Once you have determined that a connector run in Preview mode operates as expected, you can set the Preview value in your configuration to False.

Access to the svn command

Your PATH environment variable must contain a file system path where the svn command can be found. See Linux, Unix, MacOSX, and Windows documentation on how to set environment variables for use within a Unix cron job (or Windows Task Scheduler entry). Use the Unix command which svn to determine if the svn command is in your PATH.

Note: You may run the connector on a box and have it access a remote host (through ssh), which has the Subversion repository. In this case, it is not necessary to have Subversion installed on the connector box. This, however, assumes you have enabled ssh access to the remote host, and the command ssh <remote host> which svn returns a path to the svn command.

Run as a scheduled task

You can use cron (Linux) or the Task Scheduler (Windows) (or any other job-task scheduling software) to run the connector periodically. Initially, CA Agile Central recommends the connector to be run every 15 minutes during normal business hours and less frequently during non-business hours.

Command line invocation

You can have numerous configuration files in the configs subdirectory and specify any number of them for invocation. For example:

ruby svn2_agile_central.rb apricot banana cherry dogwood

In the above example, the files apricot.yml, banana.yml, cherry.yml, and dogwood.yml must exist in the configs subdirectory. The connector only looks for configuration files in the configs subdirectory (which is under the installation base directory).

The log files

When the connector is run, two different log files are updated for each configuration file named:

  • logs/svn2ca_agile_central.log —A global log file indicating the status of the connector.

    An entry is made in this log file to note the connector was invoked. For each configuration named at invocation, there will be an entry in this log file noting the return code from running the configuration. When the connector run has finished with all configurations, an entry is written to note the completion of the connector run.

  • logs/<ConfigFileName>.log

    For each configuration file named on the command line, this log file is updated with more detail about the activity that occurred during the run.

You can adjust the verbosity written to these log files by modifying the LogLevel value in the configuration file. Normally, the LogLevel would be set to Info. Should you encounter situations where the connector does not complete normally, you can adjust the LogLevel to Debug and run the connector to begin the troubleshooting process. These log files can be sent to Rally Support to expedite the investigation of a case.

Time files

The connector writes a file in the base installation directory corresponding to the configuration name with the date of the last commit processed. The file is named <configuration-name>_time.file and has a time entry in the form YYYY-mm-dd HH:MM:SS Z, for UTC (or Zulu) time. When first run, there will not be a time file for the configuration and the connector defaults to searching for commits that occurred 72 hours prior to the run of the connector. You can override that behavior by creating and editing a time file for the configuration file you are about to process. By providing an entry in the format mentioned above, you can control that point from which commits are processed.

Note: The connector will skip processing commits for a repository until there are three or more commits to process. Once there are three or more commits, the skipped commits will be processed. This is a design decision due to performance issues in Agile Central when processing the commits.

Extend the connector

Within the extension subdirectory of the installation, there is an example Ruby class in the file named statex.rb. The class definition contained in that file is named BasicActionsAndArtifactsExtractor. This example class demonstrates the basic technique of examining a commit message and extracting CA Agile Central artifact identifiers and state transition target values. Using this class when the configuration file item UpdateArtifactState value is set to True results in the transition of the State (or ScheduleState in the case of UserStory) of the identified artifact to the state value mentioned in the commit message.

For example, if there is a CA Agile Central Defect (identified as DE1987) mentioned in the commit message with a new valid state value either immediately preceding or following the artifact identifier, then the connector will change the State of the identified artifact in CA Agile Central to that state. Example:

$  svn  commit  -m  "Fixed DE1987 by changing preamble paragraph 3"  my_file.java

If CA Agile Central defect DE1987 had a state of Open prior to the commit and run of the connector, then subsequent to the operation of the connector processing this particular changeset, the state of CA Agile Central defect DE1987 would display as Fixed. Please note this message is case-sensitive, "fixed" is not the same as "Fixed".

The commit message may contain references to more than one artifact. For example, this is known to work:

$  svn   commit  -m  "Test commit msg with multiple artifacts Fixed DE9 Closed DE8"  MyFile.rb

The extension subdirectory allows you to provide your own message processing to extract CA Agile Central artifact identifiers and state changes if the example provided does not fit your conventions. Your extension must be a class written in Ruby and must provide an instance method called service which takes the commit message as an argument and must return a Ruby Hash instance with entries keyed by a State name (Fixed, Completed, and so on) or nil with a Ruby Array as the associated value populated by CA Agile Central artifact identifiers (FormattedID).

File My-Svn-proj1_time.file:

  2018-04-19 14:41:34 Z
 

File configs\My-Svn-proj1.yml:

---
VCSConnector:
 
Rally:
#   -------------------   ------------------------------------ #
#   an onprem rally...
    Server              : 10.32.16.78                          #
    Protocol            : http                                 #
    Username            : test@rallydev.com                    #
    Password            : encoded-d-d-d-d-d-d-d-d-d-d-d-=-     # encoded after first use
    Workspace           : My Sample Workspace            #
#   -------------------   ------------------------------------ #
    RepositoryName      : DogDogDog                            # name of Rally SCMRepository
#   Proxy               : server:port                          #
#   ProxyUser           : <proxy_user>                         # when using an authenticating proxy
#   ProxyPassword       : <proxy_password>                     # when using an authenticating proxy
    Lookback            : 90                                   # minutes
    UpdateArtifactState : True                                 #
    StateExtractorClass : BasicActionsAndArtifactsExtractor(message) # used if above is True
    Debug               : False                                #
 
Subversion:
#   Server              : svnsvr.company.com                   # specify if repo is not local
    RepositoryBase      : C:/Users/jpkole/vcs-svn/My-Svn-proj1 # Pathname to the centralized master Subversion repository
    Lookback            : 90                                   # minutes
    MaxItems            : 100                                  # maximum items to process in a run
#   RevURI              : http://svn/svnurial/bigproject/rev/{revnumber}             # if running web access to repo
#   FileURI             : http://svn/svnurial/bigproject/file/{revnumber}/{filepath} # if running web access
 
Services:
    Preview             : false                                # when True, show what would happen
    LogLevel            : Debug                                # default value is Info
#   PostBatchExtension  : MetricsPoster                        # for future use
 
Transforms:
Author              : FileBasedUserNameLookup(user_map.txt,":")
#   Author              : Passthru                             # the default
#   Author              : EmailAddressAsRallyUser
#   Author              : RallyUserNameLookup(FirstName,LastName)
#   Author              : UserLookupChainGang(FirstName,LastName,user_map.txt,":")
#   Author              : UserNameDomainAugmentLookup(MyDomain.com)
...

 

Troubleshooting

See log files for messages

When the connector runs, it generates two log files:

  • log/svn2ca_agile_central.log—A global log file indicating the status of the connector.
  • logs/<config-file-name>.log—For each configuration file given on the command line, this will be the log file containing information about any issues with that configuration file.

The RepositoryName is case sensitive

The configuration file contains a line like RepositoryName: Chien1, which is the name of the SCMRepository object in Rally. This name is case-sensitive. Assuming the name was mistakenly specified as chien1, you may see a log file error like:

 INFO : RallyVCSConnection.validate - SCMRepository: chien1
DEBUG : RallyVCSConnection.getSCMRepository - No SCMRepository named |chien1| in Workspace: |WS1|
 INFO : RallyVCSConnection.createSCMRepository -
        Creating SCMRepository 'chien1' (Subversion) in the 'WS1' workspace...
ERROR : UnrecoverableException (/Users/...../exceptions.rb:42 line in `initialize') -
        Unable to create SCMRepository:
        Error on request - https://rally1.rallydev.com/slm/webservice/1.40/scmrepository/create.js -
                {:errors=> ["Validation error: SCMRepository.Name:
                There is already a SCMRepository with the name 'chien1' in this Workspace"], ... ]}

Ruby Considerations

This software is written in Ruby and must be executed with a supported version of the Ruby interpreter. As of version 1.6.0 the supported Ruby version is 2.2.6. If you are running the connector on a Windows platform, you must have installed the appropriate Ruby DevKit. See Prerequisites for more information.

No Valid Artifacts Mentioned

Seen when connector tries to add a changeset to a Project the Connector User does not have permissions for

DEBUG : RallyVCSConnection.extract_artifact_references - No valid artifacts were mentioned in message
DEBUG : RallyVCSConnection._createInternal - Created Changeset: OID: 4935999999  Revision: 14d0f533084c700f Timestamp:|2016-01-06T14:58:01.000Z| (not associated with any Artifacts)

<a name="Troubleshooting-Getting-help"></a>
<h3>Get help</h3>
        <p>If you have any questions, issues, or suggestions,  click the
                        <a href="https://rally1.rallydev.com/slm/help.sp?pp=contact">Contact Support</a>
                link at the bottom of any CA Agile Central page.</p>

Revision history

  • 1.6.0-master --- 25-May-2018
    • Enhancements:
      • Unified distribution, requires use of Ruby 2.2.6 for TLS V1.2 support.
  • 1.5.3-master --- 12-Dec-2017
    • Enhancements:
      • Sync all vcs-eif connectors.
  • 1.5.1-master --- 12-Sept-2017
    • Enhancements:
      • Added Message to fields eligible for Transform.
      • Certified for use with Ruby 2.2.6.
  • 1.4.3-master --- 24-Oct-2016
    • Enhancements:
      • Updated the logic to allow for processing after 1 commit.
  • 1.4.1-master --- 17-Oct-2016
    • Fixes:
      • Addressed uncaught exception when processing an empty repository.
  • 1.4.0 - master-1046 --- 16-Nov-2015
    • Enhancements:
      • Brand redesign.

  • 1.3.2 - master-1043 --- 01-Aug-2015
    • Enhancements:
      • Added support for use of APIKey entry and revised documentation to encourage use of this in preference to use of still supported ApiKey.

  • 1.3.1 - master-1040 --- 19-Jun-2015
    • Enhancements:
      • Added support for downcasing any Rally username value, inverted sequence of retrieval from Rally and target VCS system, and upped dependency on rally_api to 1.2.1.

  • 1.3.0-master-1038 --- 29-Apr-2015
    • Fixes:
      • Handle commit messages with multi-byte characters whose length exceeds the Rally Changeset Message field length limit of 4000 bytes.
    • Enhancements:
      • Updated dependency on rally_api to 1.2.0

  • 1.2.9-cib1037 --- 10-Mar-2015
    • Fixes:
      • Refined handling of commit messages in excess of 4000 characters to account for JSON encoding expansion.

  • 1.2.8-cib1036 --- 01-Mar-2015
    • Enhancements:
      • Improved the ability to identify artifact identifiers in commit messages surrounded by bracketing characters.

  • 1.2.6-cib1035 --- 26-Jan-2015
    • Enhancements:
      • Updated rally_vcs_connection.rb configureExtensionEnvironment and statex.rb to accommodate custom artifact prefixes (such as 'BUG' for Defect).
      • Updated dependency for rally_api to version 1.1.2.

  • 1.2.5-cib1033 --- 15-Oct-2014
    • Enhancements:
      • Updated to use CA Agile Central Web Services API v2.0 and the updated rally_api gem.

  • 1.2.4-cib1031 --- 16-Sep-2014
    • Enhancements/Fixes:
      • Added support for using API Key in lieu of username and password in the Rally portion of the configuration file.
      • Updated to rally_api toolkit version 1.0.1.

  • 1.2.3-cib1030 --- 15-Sep-2014
    • Enhancements/Fixes:
      • Fixed DE21993 - to meet Rally's commit message field limitation of 4000 characters, if a commit message exceeds the character limit, characters over the limit are truncated. Upon truncation, the commit message is appended with an annotation of the truncation and a warning message displays in the log file.

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.