Troubleshooting the Subversion adapter

You may encounter these problems when using the Subversion adapter:

How do I get the queue server hostname and credentials? I need it to set up my adapter.

Adapters use a message queue server to transmit data to TeamForge Orchestrate. Adapters must therefore be configured with the queue server hostname, username, and password.

When you create a new "Source" in TeamForge Orchestrate, a unique set of queue server credentials is created for use with your adapters. To find the queue server hostname and credentials, log into TeamForge as a privileged Orchestrate user and navigate to: Pipelines > Edit desired Pipeline > Select desired Step > Edit desired Source

Locate the section named "Adapter Configuration Information".

Copy the queue server's hostname, username, and password and use them to configure your adapter.

Note that the same queue server hostname, username and password may be shared by multiple sources; however, the source association must be unique for each source.

Commits fail after installing the adapter hook script

After installing the hook script, I see an error complaining about svnlook:

Warning: post-commit hook failed (exit code 1) with output:
svnlook: Expected FS format between '1' and '4'; found format '6'
svnlook: Expected FS format between '1' and '4'; found format '6'
Traceback (most recent call last):
File "/home/user/SVN_Edge/csvn-4.0.0/data/repositories/svn_edge/hooks/post-commit", line 488, in <module>
raise Exception("post-commit failed: %s" % e)
Exception: post-commit failed: this constructor takes no arguments"

Workaround: This problem is caused by having different versions of svnlook installed: typically one in /usr/bin and another bundled with Subversion Edge. To remedy, edit the Orchestrate Subversion Adapter configuration file post_commit_orc-publish_amqp.conf and modify the "svnlook" value to point to the binary packaged with Subversion Edge (example: /home/user/SVN_Edge/current/bin).