What's New in Teamprise Client Suite V3.2?
- New Command-line Client features include Branch, Merge, and Diff
- Map projects outside your Eclipse workspace
- Build Maven projects from Team Build
- Kerberos authentication support on Linux and Mac OS X
- HP-UX on IA64 (Itanium 2) support for Teamprise Clients
What's New in Teamprise Client Suite V3.1?
- Improved Offline Support
- 64-bit support on Windows
- Many Command Line Client Improvements
- TFS 2008 SP1 New Feature Support
What's New in Teamprise Client Suite V3.0?
Command Line Client
- Check-in policies: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.
- CLC will prompt for missing credentials: 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).
- Credentials are not automatically persisted: 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.
- Destroy command: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.
- New environment variables supported: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.
- Profile support: 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.
- Resolve and associate work items during check-in: 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.
- Use of single-sign-on: 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.
- Better support for delete exclusions
- The .tpignore mechanism can now be used to exclude items from server deletion.
Performance Improvements and Bug Fixes: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.
Build Integration in Team Explorer: 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
The following features are only available against a TFS2008 server:
- Edit Retention Policies
- Keep Build
- Set Queue Priority
- Postpone Build
- Stop/Cancel Build
- Delete Build Definition
Show deleted items and undelete: 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
- Check-in policies: 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
- Check-in policy SDK: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
- Recursive compare: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
- Standard check-in policies: 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
What's New in Teamprise Client Suite V2.1?
Command Line Client
- Created a user's guide
- Enhanced workspace management
- The Teamprise command line client can now get files to standard out using the "print" command
- Recursive labels
Connections: No domain required for authentication
- Team Explorer View
- Additional work item menu options
- Better handling of server switches
- Improved refresh support
- Added message when unshelving and some items already have pending changes
- Better synchronize support
- Branch properties tab improvements
- Configurable external merge and compare tool support
- Support for linked resources
- Work Item Tracking
- Added ability to delete stored queries
- Added save button to Teamprise Explorer toolbar
- Automatic local launching of file attachments
- Better handling when associating open work items with check-ins
What's New in Teamprise Client Suite V2.0?
The focus of the Teamprise Client Suite 2.0 release is to provide full support for the work item tracking features of Visual Studio 2005 Team Foundation Server. Using Teamprise 2.0, users will be able to perform the following operations:
- Create new work items, such as bugs or tasks
- Edit existing work items
- Run work item queries stored on the Team Foundation Server
- Quick keyword search for particular work items
- Associate work items with source control check in operations
Teamprise 2.0 also completes its support for the source control features of Team Foundation Server by implementing the following operations:
- Branch and Merge
- Shelve and Unshelve
Finally, this release adds support for the Team Explorer view of Visual Studio 2005, giving users full access to the Team Foundation Server repository, including:
- Work Items
- Source Control
Access Microsoft Visual Studio 2005 or 2008 or 2008 Team Foundation Server from within the Eclipse IDE, and from Macintosh and UNIX Systems. Teamprise is a suite of client applications for accessing Microsoft Visual Studio 2005 or 2008 Team Foundation Server from outside of the Visual Studio Integrated Development Environment (IDE). Teamprise enables software development teams to use the source control, work item tracking, documents, and reporting features of Team Foundation Server from within the Eclipse IDE, and from other operating systems, including Windows based, Linux and Mac OS X.
Implemented in Java, Teamprise will run on operating systems that support a Java Runtime Environment (JRE) 1.4 or newer. Using the Teamprise Client Suite in conjunction with Visual Studio 2005 or 2008 Team System, enterprise companies can standardize on the use of Microsoft's Team Foundation Server for the Application Life-Cycle Management needs of both their .NET and Java development teams.
Plug-in for Eclipse
The Teamprise plug-in for Eclipse allows a developer to perform source control and work item tracking operations from within the Eclipse IDE. This plug-in is also compatible with IBM's WebSphere Studio for Rational Application Developer IDE. The Teamprise Plug-in for Eclipse supports Eclipse 3.0 and higher, including any Eclipse-based commercial IDEs. Access to Team System source control and work item tracking is now available to anyone developing software using Eclipse.
- Eclipse Team Provider Plug-in: As an Eclipse Team Provider Plug-in, Teamprise integrates within the standard project views to show the status of files under source control in TFS
- View and Edit Work Items:View and edit work items, such as bug reports, directly within the Eclipse IDE.
- Pending Changes View: The Teamprise Plug-in for Eclipse includes a Pending Changes View similar to that in Visual Studio, allowing developers to associate work items with source control check-in operations
- Team Explorer View: The Team Explorer View gives users full access to work items and queries, the source control repository, and project documents and reports
Teamprise includes a stand-alone, cross-platform client application which features an Explorer-style user interface for developers not working within an IDE including:
- Team Explorer View: The Team Explorer View provides access to all work items and queries, the source control repository, and project documents and reports stored in TFS
- Source Control Explorer: The Source Control Explorer provides a complete view into the TFS repository, allowing users to perform source control operations and view the status of the files in their projects
- Pending Changes View: The Pending Changes View shows the status of files that have been added, deleted, or modified by the user on their client machine
The command-line client in Teamprise is perfect for scripting and non-GUI scenarios:
- Same Command Syntax: The Teamprise Command-line Client uses the some command syntax as the version provided by Microsoft
- TFS Source Control Operations: Perform TFS Source Control check-out and check-in operations on any operating system
- Scripting Scenarios: The Teamprise Command-line Client can be used in scripting scenarios for build solutions and other automated functions