TeamForge 16.3

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 16.3 highlights

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

Check out the documentation here for more information. Here's the Release Notes with the list of new features and bug fixes. TeamForge 16.3 Update 1 is also available that includes a few critical updates to TeamForge 16.3. Check out the release notes here.

You can also see the CollabNet TeamForge training page for your TeamForge 16.3 training needs.

Git/Pull Request

  • Gerrit v2.12.2 support: TeamForge 16.3 supports Gerrit v2.12.2.
  • Pull Request: Pull request is now a fully integrated solution of the code browser component. It is a collaborative, branch-based development workflow, allowing developers and other stakeholders to review, discuss and vote on code changes before reaching the targeted branch. To know more about the feature, see Pull request overview and Pull request step-by-step.

Orchestrate/Integrations

  • Chef integration: The new TeamForge Orchestrate Chef adapter supplies deployment data from your Chef environment to TeamForge Orchestrate. Newly released integration provides associations between Chef events (such as deployments) and upstream builds and binary artifacts, extending the TeamForge traceability footprint. The integration also captures Chef data for centralized event reporting purposes. For more information, see Chef adapter overview.
  • JIRA cloud integration: Newly released webhooks-based integration (no plugin required) associates JIRA Cloud issues to TeamForge commits, extending the TeamForge traceability footprint. The integration also captures JIRA Cloud issue data for centralized event reporting purposes. For more information, see JIRA Cloud integration overview.
  • JIRA Server and Cloud integration: Added support for JIRA version 7.1.

Team and Planning Folder monitoring

Previously you could monitor only the items within a planning folder, but now monitoring can be done at the planning folder level itself. With the appropriate permission, you can also add users for monitoring them. For more information, see Monitor a planning folder.

You can now monitor a team and also items within a team. For more information, see Monitor a team.

Export artifacts to Excel (.xslx format)

MS Excel (.xlsx) format option is now available while exporting tracker artifacts from list views (tracker and planning folder), search tracker, file releases and reports pages.

Show recent repositories in My Workspace

The left pane on the My Workspace page now displays My Recent Repositories showing repositories to which five most recent commits were made by the user. Clicking the link takes you to the configured code browser for that repository.

Top navigation enhancements

Continuing with the top navigation redesin, the TeamForge web application header has the following changes:

  • You can now mark your favorite projects so that they appear at the top of your My Projects list. These selections are retained across sessions.
  • Streamlined search area featuring a visually clarified input area.

Installer/site-options.conf

POSTGRES_INTERFACE
On TeamForge servers (both single-server/distributed setups), if the first interface is not "eth0/enp0", you must set this token with the network interface card (NIC) name which PostgreSQL must listen to. For more information, see POSTGRES_INTERFACE.
JDK
TeamForge 16.3 supports JDK 1.8.0_74.

New SOAP API for monitoring objects

TeamForge 16.3 adds a new SOAP interface, IMonitoringAppSoap, for monitoring objects via SOAP APIs. Similar to setting up monitoring via Web UI, you can now set up the monitoring via SOAP APIs as well. For more information, see IMonitoringAppSoap Javadoc.

Get started with TeamForge

Tools to plan, track, search and filter

Reports

Install/Upgrade best practices

  • See Platform specification for TeamForge 16.3 and understand the software and hardware requirements.
  • See the CollabNet TeamForge 16.3 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.
  • Verify your basic networking setup before installing or upgrading TeamForge. See Set up networking for your TeamForge server.
  • Generate SSL certificates, if required, and keep them handy. See Generate SSL certificates.
  • If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
  • Create a file, /etc/security/limits.d/teamforge.conf, and make sure it has the following "nproc" and "nofile" settings.
    • vim /etc/security/limits.d/teamforge.conf
    • sf-admin soft nproc 10240
    • sf-admin hard nproc 10240
    • sf-admin hard nofile 65536
    • sf-admin soft nofile 65536
    • Save the file and reboot the server.
  • 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.
  • During upgrades, refer to the TeamForge 8.2 site-options.conf file and make sure that the TeamForge 16.3 site-options.conf file inherits all the required tokens.
    CAUTION:
    You run the risk of missing out on newly added (or removed) site option tokens if you keep reusing your site-options.conf file from an older TeamForge version on newer versions. See Site options change log for more information.
  • 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 16.3. 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

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 16.3 on a two-server distributed setup.

Three-server setup

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

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

Upgrade TeamForge

Before you begin

Attention: TeamForge installer is being optimized quite a bit. It's likely that you might come across a lot of warning messages while upgrading to TeamForge 16.3 on the same hardware (when you run the yum install teamforge command). You can safely ignore such warning messages and proceed with the upgrade.

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.2 to 16.3 on: RHEL/CentOS 6.7 server | RHEL/CentOS 7.2 server From 8.2 to 16.3 on: RHEL/CentOS 7.2 server
From 7.2 to 16.3 on RHEL/CentOS  

Two-server setup

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

Three-server setup

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

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 16.3 with other tools.

TeamForge event handlers

TeamForge APIs

Javadoc