Teamprise 3.0 Release Notes

Command Line Client

Some of the Teamprise standard check-in policies can run in the Teamprise command-line client and custom policies can be written that will also run there. Policies must be configured on Team Projects using Teamprise Explorer or Plug-in for Eclipse. Check-in policies run automatically during the check-in process if they are configured and installed on the command line client computer.

See the KB article Installing check-in policies for the command-line client for details.

In previous releases, the command line client required user credentials to be supplied through the login option for every command, except those which used a cached workspace where credentials had been saved. Teamprise CLC 3.0 will prompt at the console for username, domain, and password when it could not determine them from a profile, the workspace cache, or Windows default credentials (if available). This makes interactive use of the command line client easier.

The login option can still be supplied for all commands, and it overrides credentials that would have been loaded from profiles or cached workspaces. Use the noprompt option to disable the prompting behavior (for example, in scripts).

The command line client no longer automatically saves user credentials with its workspace cache unless the TP_AUTO_SAVE_CREDENTIALS is set (see the New environment variables supported section). This is to support customer requirements that no credentials are saved for certain configurations.

This change only affects credentials that were previously automatically saved when the workspace cache was updated. Credentials in named profiles are always saved when they are supplied.

The command line client now supports a new destroy command that can be used when connecting to a TFS 2008 server. This command can be used to permanently remove versioned item information from the server.

The TFSPROXY environment variable can be used to specify the URL of a Team Foundation download proxy to use.

How authentication credentials are stored is now controlled by the TP_AUTO_SAVE_CREDENTIALS environment variable. If this variable is not set, authentication credentials are never saved to the workspace cache.

By default, Teamprise will not connect via SSL to a TF server that does not have a trusted certificate. If the TP_ACCEPT_UNTRUSTED_CERTIFICATES environment variable is set, this restriction is relaxed, and Teamprise will connect to untrusted servers.

The command line client now supports profiles. Profiles store information needed to make a connection to a Team Foundation server. You can enter this information once by creating a profile, and then use that profile with the profile option instead of entering the connection details repeatedly.

Use the profile command to create and edit profiles. Use the profiles command to list the configured profiles.

The command line client's checkin command now supports two new options, associate and resolve. The associate option can be used to associate the changeset with one or more specified work items. The resolve option resolves the specified work items and links them to the changeset.

The command line client now supports single sign-on on Windows. If you don't specify the -login option or specify a profile that doesn't contain credential information, the credentials of the user running the command line client are used to authenticate to the TF server.

Eclipse Plugin

The .tpignore mechanism can now be used to exclude items from server deletion.

General

Numerous small bug fixes and performance improvements have been included in this release including all fixes from issues reported by customers using the 2.x versions of the Teamprise Client Suite.

Additionally, when supported by Team Foundation Server, messages sent from TFS to Teamprise will be compressed. Previously this was just the case for file transfers and not general web service traffic. The change was made to match the default behaviour of the Microsoft Visual Studio Team Explorer client. Over a low bandwidth connection, the performance improvement experienced can be significantly. If desired, this behaviour can be disabled in Teamprise by setting the Java system property Teamprise.soap.disable-gzip to true.

Integration

The Teamprise TFS Ant tasks have been updated to version 1.2. See the Ant task manual for a full changelog.

Team Build

Teamprise now integrates with the Build Services on Team Foundation Server and provides a "Builds" node in the Team Explorer view as well as a Build Explorer and build management capabilities. The Teamprise client has been written to take advantage of the new build facilities provided by Team Foundation Server 2008, therefore if used to connect to a Team Foundation Server 2005 instance some features will be unavailable.

The following features are implemented in the plug-in for Eclipse as well as Teamprise Explorer and work with both TS2005 and TFS2008:

• View existing build definitions
• Build Explorer
• Queue new builds
• View build report
• Edit Build Quality
• Delete build
• Manage Build Qualities
• Open Drop Folder
• New/Edit Build Definition

• Edit Retention Policies
• Keep Build
• Set Queue Priority
• Postpone Build
• Stop/Cancel Build
• Delete Build Definition

For instructions on building Ant based projects from Team Build see the following blog post http://www.woodwardweb.com/teamprise/000406.html

• Open Drop Folder may not work in some Unix environments without GTK.
• No Build Command Line Client (TfsBuild)

Team Explorer

Teamprise can now show deleted items in the Source Control Editor. Display of deleted items is controlled by a new preference:

Many operations are available on deleted items, such as history, get, properties, etc. In addition, Teamprise supports undeleting deleted items:

Version Control

Teamprise now supports check-in policies. Check-in policies are used to perform additional checking before committing a changeset to the TF server. Check-in policy warnings are reported in a new tab in the Pending Changes view:

Check-in policies can be configured by an administrator for a Team Project using the Team Explorer view:

Some check-in policies are also supported in the command line client.

To go with the new check-in policies feature, Teamprise provides a check-in policy SDK that can be used by customers to develop custom check-in policies. The SDK includes documentation and sample code.

Teamprise now supports recursive compare in Teamprise Explorer and the Teamprise Plug-in for Eclipse. Any server or local folder can be compared to any other server or local folder.

Teamprise provides several standard check-in policies that are available by default. These include a forbidden patterns policy, a work item policy, a changeset comments policy, and a build policy.

Work Item Tracking

Teamprise now supports the ALLOWEXISTINGVALUE rule. This rule can be used in conjunction with certain other rules to allow existing values in fields that would otherwise be disallowed.