Released on: 26
October,
2015
8.1 Patch 1 installation instructions:
Apply
TeamForge
8.1 Patch 1 (8.1.0.1) if
you have
TeamForge
8.1 (8.1.0.0) up and
running.
Enhancements/Upgrades
Internal code browser
CollabNet’s native code browser is now a default option for both Subversion and Git
integration servers.
Add
SSLProtocolSuite and SSLCipherSuite as tokens
The CipherSuite configuration is now possible via
site-options.conf tokens. For more information, see SSL_PROTOCOL and SSL_CIPHER_SUITE.
Software version upgrades
Subversion has been upgraded to 1.8.14.
Fixed bugs
Reports
The following Reports related issues have been fixed:
- Minor alignment issues found in some of the 'Project Statistics' component's
reports such as the Commits report
(with
'Date' on the X
axis)
have been fixed.
- The incorrect sequence generation of the report_parameter
table that caused the TeamForge 8.0 to 8.1 migration failure has been
fixed.
- An issue occurred while exporting table reports if values were selected from the
'Select Users' flex field. This has been fixed.
- The issue with the display of the report title on CLI reports has been
fixed.
- Tracker report creation failed when any status other than 'Any', 'All Open' or
'All Closed' was specified. This has been fixed.
- The Group By filter was working correctly and report artifacts were displayed
under their appropriate group only when the Fields Shown in
Report(s) value was the same as that of Group
By. This has been fixed.
- The help text that appears on hovering the mouse over Select
Tracker(s) and Select Planning Folder(s)
fields has been removed from all the relevant reports.
- The Assigned To field on the generated Distribution
reports now correctly displays the user's full name and not the user
name.
SCM
The following code browser issues have been fixed:
- Links to Gerrit reviews are now not shown when browsing a
replica.
- On the code browser, while switching to a branch/tag where a subdirectory does
not exist, a 404 error is now
displayed.
- The pin/last Diff link was throwing an irrelevant error across renames. This has
been fixed.
- Unnecessary UI options have been removed from the code browser tree
view.
- Inconsistent behavior around pin links and parsing issue in code browser have
been fixed.
- If any database operation failed during the transition of the replication
command status, the whole execution rolled back causing inaccurate replication
statuses.This has been fixed.
- If Orchestrate is not installed properly, the
Associations tab is no longer displayed on the
TeamForge code browser.
Installer
An issue that resulted in long JBOSS startup time on certain configurations has now
been fixed.
Build and Test
When SVN was on a separate server, clicking the Build and Test
link on the TeamForge page was not opening the appropriate Jenkins page when
displayed in an iframe. This has been fixed.
Project Home
An issue occurred while accessing files in the publishing
repository through the relative URL /www. This has been
fixed.
SOAP
The following SOAP related issues have been fixed:
- SOAP services failed intermittently when multiple SOAP calls were executed
in parallel. This has been fixed.
- When trying to fetch a large number of repositories from an
external system, a time out error occurred. This has been fixed.
UI/UX
An issue occurred with pop-up windows on the View Artifact page
for some special characters in the Status field.
IAF
SVN commit details were not getting associated with the Project Tracker ID because of
which they were not showing up on the Project Tracker artifact page.This has been
fixed.
Security
This patch addresses few information disclosure related security issues.
Tracker
The following Tracker related issues have been fixed:
- A concurrency issue around artifact activities has been
fixed.
- Disabling the tracker Points field in Tracker
Settings resulted in invalid values being shown on the
Planning Folder Summary page. This has been fixed.
- An issue around deleting a tracker has been fixed.
- The issue with the Points value not getting updated when
the Calculate Points field (Tracker Settings) was
disabled has been fixed.
- The value 'None' was appearing twice in a user-defined and required drop-down
field. This has been fixed.
Kanban board
When the child artifact card is dragged from one swimlane to another, the parent
artifact card now displays correct values of the total number of Open and Closed
artifacts.
Git
Changes have been made to ensure that if a Git repository is removed, its mirrors on
replica servers are removed as well.
Orchestrate
The following Orchestrate related issues have been addressed:
- Migration from version 1.4.0 is now fully supported. Release 1.4.0
superseded immediately with a patch and was not intended for customer
consumption.
- When Orchestrate is deactivated and reinstated at the project level, old
sources would remain intact. This has been remedied in this patch such that
all old sources are now deleted.
- Several upgrade related data migration bugs have been addressed.
- When projects are created from a template, Orchestrate created duplicate
sources. This issue has been resolved.
- Installation can be resumed if there is an "IAF registration" failure.
- Installation properly updates RabbitMQ credentials when installation is run
multiple times.
- Upgrade and installation will no longer permit "localhost" for the RabbitMQ
FQDN. Using a local value prevents users from obtaining the real FQDN,
needed during source setup.
- Better support for installing Orchestrate in non-SSL (http) mode.
- Better handling of Orchestrate objects during project deletion.
- A bug in the Orchestrate icon service related to paths has been fixed.
Known issues
Git
You cannot browse Git repositories if you have Git on a separate server with SSL
turned off, a 404 error message shows up.
For
troubleshooting the issue, see this
topic.
Discussion forum
An issue prevents all but trusted users and moderators from posting to 'Moderated'
discussion forums via email.
Project dashboard
Concurrent access to dashboards on sites with large number of projects could result
in system errors.
Integrated applications
Exporting integrated application configurations could sometimes result in system
outages.