TeamForge 8.2

CollabNet TeamForge® is the industry's only open and extensible collaborative software delivery platform for distributed teams. It enables organizations to improve collaboration, agility and governance by connecting teams, processes, IP and tools via a centralized, secure, web-based system. With TeamForge, your entire organization can collaborate and become more agile at scale. And it scales to tens of thousands of users.

TeamForge 8.2 highlights

Check out the cool new features and enhancements to TeamForge with its new 8.2 release.

Check out the documentation here for more information. Here's the Release Notes with the list of new features and bug fixes. You can also see the CollabNet TeamForge training page for your TeamForge 8.2 training needs.

User experience improvements
  • Navigation – My Workspace
    Click to expand
  • Navigation – Admin Menu
    Click to expand
  • Navigation – Project Menu
    Click to expand
Association Viewer
  • The TeamForge Association Viewer is available for objects with Associations tabs or options.
    Click to expand
  • Use Trace to expand the viewer for more detailed traceability.
    Click to expand
Typed planning folders
  • When you create your Planning Folder, you can now choose the folder type using the folder type buttons.
    Click to expand
Improved Kanban Board
  • Add artifacts
    Click to expand
  • Recently Closed View
    Click to expand
  • Task and Kanban Board – Rank / Organize Artifacts
    Click to expand
SCM – Code Browser Enhancements
  • Association Viewer
    Click to expand
  • Git Support – Changes Tab
    click to expand
  • Git Support – Git Revision Graph
    Click to expand
  • Git Support – History Protect UI
    Click to expand
  • Git Support – Branch Comparison
    Click to expand
  • Git Support – Sub-module Support
    Click to expand
  • Git Support – Gerrit Code Review
    Click to expand
Reporting
  • Explore Feature
    Click to expand
  • Cross Project Tracker Table
    Click to expand
Tracker
  • Tracker Default Priority
    Click to expand
  • Select Artifact Export
    Click to expand
Project Home page - Search with Custom Fields
Click to expand

Get started with TeamForge

Start collaborating in TeamForge now.
Are you a TeamForge user? Start working on a TeamForge project
Are you a TeamForge project manager? Create and manage projects in TeamForge
Are you a TeamForge site administrator? Click here to know more about how to run a site

Here's what it takes to work with TeamForge or lead TeamForge projects.

For project managers For project members
Project Dashboard Log on to TeamForge
Create projects Change password
Build your project home page My Page/My Workspace
Set up trackers Work with trackers
Create tracker work flows Work on tasks
Set up planning folders Work with documents
Manage your project with Teams Collaborate via discussion forums and mailing lists
Manage task work flow Work with source code
Generate reports Manage binaries
Control project access Provision hardware using Lab Management
Manage project membership Build and test your software
Work with linked and integrated applications Work with file releases
Provision hardware using Lab Management Monitor TeamForge work items
  Wiki syntax

Tools to plan, track, search and filter

Search and filter Boards
Quick/Advanced search Planning Board
Tracker search Task Board
Task search Kanban Board
Filters  
Full-text search  

Reports

Activity reports Agile reports Distribution reports Trend reports
SCM Commits Cumulative Flow Chart Status Distribution by Area/Group Average Age Report
Artifact Created Release Burn Up Chart Total Size by Area/Group Artifact Open/Close Chart (Multiple Trackers)
Artifact Closed Burn Down Chart Average Size by Area/Group  
Build Activity Committed vs Done vs Missed Total Size by Tracker Type  
Build and Test Activity   Artifact Distribution Chart (Multiple Trackers)  
Commit Activity   Artifact Distribution Chart (Single Tracker)  
Commits by User      
File Changes Over Time      
Table reports Datamart CLI reports
Table reports: Task and Tracker reports TeamForge datamart schema CLI reports framework
  Access TeamForge datamart using external tools Upgrade CLI reports

Install/Upgrade best practices

  • See Platform specification for TeamForge 8.2 and understand the software and hardware requirements.
  • See the CollabNet TeamForge 8.2 release notes and know more about the TeamForge version you want to install or upgrade to.
  • Plan your installation or upgrade. See Plan your installation | Plan your upgrade
  • Do not customize your operating system installation. Select only the default packages list.
  • If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
  • You must have no tasks in progress while uninstalling the CLI add-ons during the upgrade process.
  • Look for new or modified site-options.conf tokens and update your site-options.conf file as required during the upgrade process.
  • Always use the site-options-dedicated.conf file that's packaged with the TeamForge version you are upgrading to. Refer to the TeamForge 8.1 site-options.conf file and make sure that the TeamForge 8.2 site-options.conf file inherits all the required tokens.
    CAUTION:
    You run the risk of missing out on newly added site option tokens if you keep reusing your site-options.conf file from an older TeamForge version on newer versions.
  • Do not manually modify TeamForge-managed site option tokens such as the AUTO_DATA token. See AUTO_DATA for more information.
  • No backup is required for same hardware upgrades. However, you can create a backup as a precaution. See Back up and restore CollabNet TeamForge data to learn more about backing up TeamForge database and file system.
  • Always use compatible JDBC drivers meant for specific database versions. See JDBC Drivers Reference for more information. Also see: Why do ETL jobs fail post TeamForge upgrade?
  • You can run the initial load job any time after the site is upgraded to TeamForge 8.2. We recommend that you run it before you hand over the site to the users. For more information, see When do I run the initial load job?

Install TeamForge

Before you begin

Platform information | Software requirements
How many servers are required to run TeamForge?
Plan your installation | Set up networking | Open ports
Installation FAQs

Single-server setup

All services on a single: RHEL/CentOS 7.2 server | RHEL/CentOS 6.7 server

Two-server setup

Refer to the following topics if you plan to install TeamForge 8.2 on a two-server distributed setup.

RHEL/CentOS 7.2
Install TeamForge 8.2 on a server and:
Database and Datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
SCM and Git on a separate server
Oracle database on a separate server
Git on a separate server

Three-server setup

Refer to the following topic if you plan to install TeamForge 8.2 on a three-server distributed setup.

Install TeamForge 8.2 on a server and Database and SCM on separate servers

Post installation

Supply license key: From TeamForge user interface | As a text file
Verify your TeamForge 8.2 installation
Maintain your site | Perform common administration tasks

Install TeamForge on VMware Player or VMware ESXi

Hardware and software requirements for CollabNet TeamForge 8.2 on a virtual machine
Install TeamForge 8.2 on: VMware Player | ESXi
Configure CollabNet TeamForge on VMware Player
Supply your TeamForge license key

Upgrade TeamForge

Before you begin

Platform information | Software requirements
How many servers are required to run TeamForge? | Should I upgrade to TeamForge 8.2 on a new server?
Plan your upgrade
Upgrade FAQs

Single-server setup

You may choose to upgrade on the same hardware or new hardware. Refer to the topic that suits your needs.

Upgrade on same hardware Upgrade on new hardware
From 8.1 to 8.2 on: RHEL/CentOS 6.7 server | RHEL/CentOS 7.2 server From 8.1 to 8.2 on: RHEL/CentOS 7.2 server
From 7.1 to 8.2 on RHEL/CentOS  

Two-server setup

Refer to the following topics if you have TeamForge 8.1 running on a two-server distributed setup and are planning to upgrade to TeamForge 8.2 on the same hardware.

RHEL/CentOS 6.7
Upgrade TeamForge on a server and:
Database and datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
Git on a separate server
Oracle database on a separate server
RHEL/CentOS 7.2
Upgrade TeamForge on a server and:
Database and datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
Git on a separate server
Oracle database on a separate server

Three-server setup

Refer to the following topics if you have TeamForge 8.1 running on a three-server distributed setup and are planning to upgrade to TeamForge 8.2 on the same hardware.

RHEL/CentOS 6.7
Upgrade TeamForge on a server and Database and SCM on separate servers
RHEL/CentOS 7.2
Upgrade TeamForge on a server and Database and SCM on separate servers

Integrate TeamForge with third-party tools

TeamForge supports integrations with third-party tools for versioning, reviewing, searching source code, binary repository management and test management. For more information, see Integrate TeamForge 8.2 with other tools.

TeamForge event handlers

Custom event handling framework, examples and best practices
How to create a new event file?

TeamForge APIs

Note: API50 is present for backward compatibility and may be removed in future. API44 and API43 are removed completely.
What can I do with the SOAP API?
Get started with the CollabNet TeamForge SOAP API
Update an application to the TeamForge 8.2 API
How does an application interact with TeamForge SOAP services?
TeamForge services available via SOAP

Javadoc

Javadoc index