Check command history in TeamForge

Recent command history for a replica server or a specific repository allows you to check for errors and see whether there are pending commands.

At the site level, you can see the status of the entire replica server and event queue including the event being actively processed. You can also see this at the repository level from within a TeamForge project. >

If a repository revision is not showing up, for example, you can check for errors to know it's not just because the repository is still busy synching the latest revision. You can also check whether there are commands waiting in the queue and whether the repository is truly in synch.

To check the command history for a replica repository, follow these steps:
1. Click Source Code in the project navigation bar.
2. In the list of repositories, click the icon for the one you're interested in. You'll see repository details and command history. Here's an example:
  
  Tip: You can also check command history by clicking on the Status icon in the Edit repository page.
You need to be a TeamForge administrator to check the command history across a replica server.
1. On the site administration navigation bar, click Integrations.
2. On the SCM Integrations page, click the name of the replica server you're interested in. The Edit System page displays the command history.

From within the event list, you can click on a failure to be taken to the Subversion Edge console and the log file with the details of the problem.

You can also monitor current activity. For example, suppose there is a new repository initialization that has been synching for several hours and you want to get an idea of how far it has progressed. You can click the event to be taken to the Subversion Edge server where the output of the svnsync process is tailed. You can then see what svnsync is doing and get an idea of what revision it is processing.