The TeamForge 21.0 release incorporates new features and enhancements that reinforce and expand the unique value of TeamForge. Read more to know what's new!

Release Information

  • Released on: Mar 5, 2021
  • GA Version: 21.0.303

TeamForge Rebranding

The TeamForge application has been rebranded according to the branding guidelines. Here’s a list of changes done as part of this rebranding exercise.

  • A new TeamForge product logo
    TeamForge product logo
    Custom Logo Guidelines

    Follow these guidelines if you want to use a custom logo.

    • The logo can be of any format—PNG, GIF, JPEG, and SVG. However, use a transparent format such as SVG. JPEG files, for example, are not transparent.
    • The logo can be of any size, but choose the aspect ratio appropriately. However, the logo width should be at least 100px.
  • A new graphic image on the Welcome and Login pages
    TeamForge welcome image
  • Changed the color of the top Navigation bar
    TeamForge top nav bar color
  • Changed the color of the primary and secondary command buttons
  • Changed the color of the Notification bar at the top
  • Changed the Favicon

TeamForge Baselines—Glob Pattern Search for Binary Packages

You can now use glob patterns to search for and select binary packages when you create or edit baselines (including project baselines) and baseline definitions.

Select the server and repository from the Server and Repository drop-down lists, and select one or more packages from the Select Packages drop-down list.

  • The Select Packages drop-down list lets you search for packages using glob patterns.
  • The Select Packages drop-down list loads the first 100 packages to start with.
  • You must search for packages using file path glob patterns if you do not find what you are looking for.
  • For example, use the com/**/*.jar glob pattern to recursively search for JAR files in the com folder.

    Glob pattern search for binary packages


  • Added tootltips to icons, command buttons and other form objects for better user assistance.
    Tooltips for icons and command buttons
  • Form validation enhancements to the Create New Documents and Documents List pages—improved form validation messages for better user assistance in case of form submission errors.
    Form validation messages


Here’s a list of what’s new with integrations supported by TeamForge 21.0.

Support for Nexus 3.28
TeamForge 21.0 supports integration with Nexus 3.29.2. For more information, see Install or Upgrade the TeamForge—Nexus Integration Plugin.

My Workspace Artifacts Widget

Suppose you have configured the maximum number of artifacts to show in the My workspace Artifacts widget. If the number of artifacts exceeds your preferred number of artifacts to show, a View All link shows up.

Clicking the View All link shows the entire list of artifacts assigned to you on the All My Assigned Artifacts page. However, out of all the filters you may have configured in the Artifacts widget, the All My Assigned Artifacts page can only inherit and apply the following filters:

  • Priority
  • Created By
  • Status
  • Tracker
  • Project

For example, you might have used the Date Submitted filter of the Artifacts widget to filter and view only those artifacts submitted in the last 90 days. However, when you click View All, the All My Assigned Artifacts page shows all the artifacts assigned to you regardless of the date of submission.

For more information, see My Workspace.

TeamForge SCM—Enterprise Version Control

TeamForge—Git Integration 21.0.4-3.2.7

For more information about vanilla Gerrit version 3.2, see Gerrit 3.2.7 Release Notes.

Branch and Tag Naming Conventions

  • You can now enforce standard naming conventions for Git branches and tags via regular expressions.
  • For example, you can have branch and tag names to have only lower case, start with releases/, and so on.
  • This can be done for select repositories or for a set of repositories in a project.
    Branch and Tag naming conventions

Protected Branches—Role and User Based Restrictions on push and merge

  • You can now create protected branches with more restrictions.
  • You can set both role-based and user-based access permissions to restrict certain operations such as direct push, history rewrite (force push), and merge on the protected branches.
    Enhanced protected branches

Work Item Status-based Commit Governance

  • You can now build and enforce a commit governance policy that is based on work item statuses.
  • Select the list of allowed work item statuses for commits as part of your Tracker settings.
  • Code changes associated with work items that are in disallowed statuses are rejected.
    Work item status-based commit governance

Resolvable Code Inline Comments

You can now mark review comments in a code review as resolved/unresolved. Unresolved review comments, if any, are automatically posted for resolution when the repository maintainer tries to merge the code change.

Trigger Jenkins Jobs via Webhooks

  • In addition to Jenkins Gerrit Trigger plugin, you can now make the Gerrit code reviews plugin to work with TeamForge.
  • You no longer have to bother about the long-living SSH tunnel issues (the plugin no longer uses SSH tunnel for the connection between Jenkins and TeamForge) as the new plugin supports Webhook-based job triggering.
    Trigger Jenkins jobs via Webhooks

Other Enhancements

  • Git submodule can now be updated to any arbitrary remote repository revision.
  • Review panel and other right hand side panels now stick to top of the review page
  • Long code browser breadcrumbs are now truncated to fit smaller viewport.
  • Validation message shown when it is not possible to merge a change due to duplicate email addresses.
  • File upload and creation operations are now separated.

Gerrit Upgrade from Version 2.16 to 3.2

TeamForge 20.3 and later support Gerrit 3.2—a major upgrade that skips two Gerrit versions—3.0 and 3.1 and includes the following note-worthy changes:

  • TeamForge 20.3 (and later) Gerrit is not data-compatible with Gerrit 2.16 or earlier (in other words, not data-compatible with TeamForge 20.0 or earlier). Intermediate data migration to Gerrit 2.16 happens when you upgrade from TeamForge 20.0 or earlier to TeamForge 20.3 (or later). This means that data migration during upgrade takes more than usual time to complete.
  • TeamForge 20.3 (and later) Gerrit is not index-compatible with any previous version. All open reviews are reindexed offline when you upgrade from TeamForge 20.0 or earlier to TeamForge 20.3 (or later). This means that data migration during upgrade takes more than usual time to complete.
  • Orphaned draft comments are cleaned up when you upgrade to TeamForge 20.3 (or later). It is recommended to schedule and run the following Git garbage collection (Git GC) command directly on the All-Users project before you upgrade to TeamForge 20.3 (or later).
    ssh -p 29418 [admin]@[git-server] gerrit gc All-Users --aggressive --show-progress
  • Git Protocol v2 is now default
  • ReviewDB and Gerrit GWT UIs are no longer available
  • For more information about Git protocol v2, see the documentation for Git Protocol v2.
  • ReviewDB removal means that the database backend for changes, accounts, groups and projects (ReviewDb) is removed and this metadata is now stored in git (“NoteDb”). As NoteDb is being used by TeamForge 19.0 and later, this change is seamless for the users.
  • However, the Gerrit GWT UI has more visible consequences. The GWT-related UI plugin functionality had to be ported—either to the new Gerrit Polymer UI or to the TeamForge UI.
Noteworthy Changes
The Gerrit UI has a new look and feel with the new Gerrit Polymer UI replacing the GWT UI.
The Gerrit UI no longer has the history protection tab. This functionality is now available via the TeamForge Code Browser UI.
Gerrit internal repositories are exposed at the integration level in TeamForge.
Microsoft Internet Explorer 11 is no longer supported in Gerrit UI.

Install / Upgrade

  • TeamForge 21.0 supports both RHEL 8.3 and RHEL/CentOS 7.9.
  • RHEL/CentOS 6.10 is no longer supported.
Tags for this page: getting_started