New features in TeamForge 17.4

You can create one or more dashboards to categorize and view data in many different views. For instance, you may decide to create three dashboards: Dashboard A, B and C. With these three dashboards, you may choose to configure Dashboard A and B to view events from projects A and B respectively and configure Dashboard C to view just the code reviews. For more information, see My Workspace.

TeamForge 17.4 introduces Advanced Transition settings, which you can use to make specific fields as 'required' and also to show or hide specific fields when a status transition happens. Advanced Transition settings are applied when you create or edit artifacts in a tracker and only when you edit artifacts in Planning, Task, and Kanban boards. For more information, see Create a tracker workflow.

• Based on vanilla Gerritt v2.13.8. See Gerrit v2.13.8 release notes for more information.
• Git installer enhancements to support TeamForge 17.4 installer enhancements.
• User interface performance enhancements to better support branches and Gerrit reviews that are substantially large in size.
• GERRIT_FORCE_HISTORY_PROTECTION site-options token is no longer supported. Remove this token from the site-options.conf file while upgrading to TeamForge 17.4 or later. History Protection is enabled by default in TeamForge 17.4 and later. However, Site Administrators can disable History Protection at the site level if need be, after which Project Administrators can choose to have History Protection enabled or disabled for individual repositories.

• Based on 2.13.9 vanilla Gerrit version released on 2 August, 2017. See v2.13.9 for more information.
• Fixed the issue in which the RabbitMQ connections and threads are kept permanently in memory even if the project is not active currently.

  Cause of the issue:

  This issue is caused by the default configuration of RabbitMQ client which opens the dedicated thread pool (that spawns up to 2 * number of CPU threads by default) per connection. The issue manifests with large number of threads being spawned over time up to,
  • (number of repositories + number of projects) for threads named AMQP Connection AA.BB.CC.DD.YYYY.
  • (number of repositories + number of projects) * (2 * number of CPUs) for threads named pool-XXX-thread-Y (especially when the machine is heavily loaded and multiple changes are being reviewed and pushed to multiple projects).

  Solution:

  • Shared thread pool used by all RabbitMQ connections: It can spawn up to (factor * number of CPUs) threads where factor can be modified by setting teamforge.notificationMaxRabbitMQExecutorsFactor in gerrit.config (default value is 2) file. Threads are removed from thread pool after being idle for more than teamforge.notificationMaxRabbitMqThreadIdleTime seconds in gerrit.config (by default 3*60s) file. This addresses the issue with the pool-XXX-thread-Y threads explosion.
  • Connection Expiration: Connection to get closed after being idle for more than teamforge.notificationMaxRabbitMQConnectionIdleTime seconds in gerrit.config (default is 5*60s) file. This addresses the issue with the AMQP Connection AA.BB.CC.DD:YYYY threads explosion as they are not being quickly (marked as "not used" after teamforge.notificationMaxRabbitMQConnectionIdleTime idle time and guaranteed to be collected within (2 * teamforge.notificationMaxRabbitMQConnectionIdleTime idle time)) collected.
• You can now search for the changes using Change-Id triplet (Repository~Ref~Change-Id). When the first 5 characters of the Repository name (Example: IdeaField) matches the Change-Id pattern, the changes searched for will be shown. This fix is sent back to open source Gerrit.

• For the vanilla based Gerrit release notes and the bug fixes, see Gerrit v2.13.9-11-gf25da13683 released on November 3, 2017.

• HTTP webhooks functionality has been implemented to set up communication between TeamForge Git integration and the following products:

  • Lifecycle
  • Continuum
  • DLM 2.0
  • Any other tool that accepts HTTP notifications

  TeamForge UI for webhooks (implemented in TeamForge 17.11) is not backported. However, you can use the following products to configure webhooks:

  • CollabNet Desktop (latest development version)
  • GitEye (latest development version)
  • TeamForge WebHooks Configurator

• Bug fixes

  Critical upstream (stable-2.13) Gerrit fix is now available for SSH clone/fetch failure when server takes more than 30 seconds to compute its operation. To handle this, a new parameter sshd.waitTimeout has been included in the gerrit.config file. By default, the value of this parameter is 30 seconds.

As a result of EventQ installer changes, the following EventQ tokens are no longer required/supported (see Site options change log).

• ORC_HOSTNAME
• ORC_SSL_CA_CERT_FILE
• ORC_PORT
• ORC_PROXIED_PATH
• ORC_PROTOCOL
• ORCHESTRATE_ENABLED
• POSTGRES_INTERFACE_IP
• POSTGRES_INTERFACE

Changes to supported software versions

• Postgres 9.6.1
• James 2.3.2.1

# CTF Core
SCM_ADMIN_PASSWORD=$auto$
IAF_DBPASS=$auto$
SCM_DEFAULT_SHARED_SECRET=$auto$
SOAP_ANONYMOUS_SHARED_SECRET=$auto$

# Database
DATABASE_USERNAME=teamforge
DATABASE_NAME=teamforge
DATABASE_PASSWORD=$auto$
DATABASE_READ_ONLY_USER=teamforge_reader
DATABASE_READ_ONLY_PASSWORD=$auto$

# Datamart
REPORTS_DATABASE_USERNAME=teamforge_datamart
REPORTS_DATABASE_NAME=teamforge_datamart
REPORTS_DATABASE_PASSWORD=$auto$
REPORTS_DATABASE_READ_ONLY_USER=teamforge_datamart_reader
REPORTS_DATABASE_READ_ONLY_PASSWORD=$auto$

# ETL
ETL_SOAP_SHARED_SECRET=$auto$

# Gerrit
GERRIT_DATABASE_PASSWORD=$auto$

# RabbitMQ
RABBITMQ_APP_ADMIN_USER=guest
RABBITMQ_APP_ADMIN_PASSWORD=$auto$
RABBITMQ_APP_CTF_USER=ctf
RABBITMQ_APP_CTF_PASSWORD=$auto$
RABBITMQ_APP_SERVICES_USER=eventq
RABBITMQ_APP_SERVICES_PASSWORD=$auto$
RABBITMQ_PERMISSION_PUBLISHER=permission_publisher
RABBITMQ_PERMISSION_PUBLISHER_PASSWORD=$auto$

# Mongo
MONGODB_APP_DATABASE_NAME=eventq
MONGODB_ADMIN_DATABASE_NAME=admin
MONGODB_APP_ADMIN_USER=admin
MONGODB_APP_ADMIN_PASSWORD=$auto$
MONGODB_APP_BACKUP_USER=backup
MONGODB_APP_BACKUP_PASSWORD=$auto$
MONGODB_APP_SERVICES_USER=eventq
MONGODB_APP_SERVICES_PASSWORD=$auto$

# HAProxy
HAPROXY_STATS_PASSWORD=$auto$

# Binary
IAF_DBNAME=iafdb
IAF_DBUSER=iafdbusr

# James Admin (for management interface)
JAMES_ADMIN_USER=admin
JAMES_ADMIN_PASSWORD=$auto$

For example:

mypostgresserver:LISTEN_IP = 1.2.3.4
localhost:mail:LISTEN_IP = 1.2.3.4

More changes

• The is_service_running.py script is no longer available.
• TeamForge 17.4 installer expects the system locale to be LANG=en_US.UTF-8. TeamForge create runtime (/opt/collabnet/teamforge/bin/teamforge provision) fails otherwise.
• The Review Board application, which was used to be installed only on the TeamForge Application Server, can now be installed on a separate server.
• The default Review Board data directory has been changed from /opt/collabnet/reaviewboard/data to /opt/collabnet/teamforge/var/reviewboard/data in TeamForge 17.4. Make sure you restore your Review Board backup to the new data directory, which is /opt/collabnet/teamforge/var/reviewboard/data.
• The publish/remotePublishLog is now being generated in /opt/collabnet/teamforge/log-archive/others/ as expected.
• As PostgreSQL upgrade is taken care of by the teamforge script during teamforge provision, pgturant utility is no longer required and therefore not supported any longer.
• CEE compatibility mode is no longer supported.
• Warning messages displayed during the installation or upgrade are now changed from "Yellow" to "Amber" color.
• For a list of obsolete and new site option tokens in TeamForge 17.4, see Site options change log.