- Released on: October 31, 2018
- GA Version: 18.3.612
SAML Authentication to Access Non-web Applications
In the past, users authenticated via SAML were able to access web applications only. With TeamForge 18.3, users in a SAML-enabled environment can access non-web applications too using their TeamForge credentials. For more information, see Authenticate SAML Users to Access Non-web Applications.
What’s new with the Configure Application Page?
ENABLE LOCAL USER and ENABLE ACCOUNT MANAGEMENT
In the past, site administrators were able to perform the following two tasks, designate users as local users and manage user accounts and passwords, by enabling a single site option ALLOW LOCAL USER (System Tools > Configure Application).
To manage these two tasks distinctly, the ALLOW LOCAL USER parameter is now replaced with two new site options, ENABLE LOCAL USER and ENABLE ACCOUNT MANAGEMENT.
ENABLE LDAP SELF REGISTRATION
This is a new site option added in TeamForge 18.3. If LDAP is enabled as an IdP, the site option ENABLE LDAP SELF REGISTRATION, which is enabled by default, redirects those who try to log on to TeamForge without a user account, to the Create TeamForge Account page. For more information, see ENABLE LDAP SELF REGISTRATION.
Following the Beta release of the Baseline feature in TeamForge 18.2, TeamForge 18.3 brings you the release candidate of the Baseline feature.
A Baseline in TeamForge represents an approved snapshot of selected configuration items from a given TeamForge project at a given point in time. Here’s a list of links you can refer to know more about TeamForge Baseline.
- Baseline - An Overview
- Create Baseline
- Edit Baseline
- Review Baseline
- View Baseline
- Compare Baselines
- Search Baseline
- Create Baseline Definition
- Edit Baseline Definition
- View Baseline Definition
- Compare Baseline Definitions
- Search Baseline Definition
Project Baseline Definition
- Manage Custom Attributes
- Manage Custom Statuses
- Manage Workflow Status Transition
- Manage Field Inclusions
Baseline REST API Documentation
Compare Baselines feature is supported in the following browsers:
- Google Chrome
- Microsoft Edge
- Mozilla Firefox
Baseline Service to Synchronize User Information
A new service
baseline-post-install has been added in TeamForge 18.3. This is the baseline service that is used to synchronize user information between the Baseline and TeamForge databases.
Here’s the list of changes related to the My Artifacts widget of My Workspace.
Filter Artifacts by Title—You can now search artifact titles for specific keywords and filter them. Click the Title header on the My Artifacts widget and type your keyword to view the list of matching artifacts as you type.
View Monitored Artifacts—You can now view the artifacts that you’re monitoring using the Include Monitored by Me option.
For more information, see My Artifacts Widget.
The Tasks component that was deprecated a while ago has been removed from TeamForge 18.3 (and later). However, legacy Tasks data, if any, continues to exist in the TeamForge database. Contact the CollabNet Support in case you need any assistance with the Tasks component or its data.
The New Webhooks-based Event Broker
TeamForge-Jenkins Integration Using the TeamForge Webhooks-based Event Broker
TeamForge 18.3 is equipped with a native webhooks-based event broker for integrations. For more information, see TeamForge Webhooks-based Event Broker.
The Webhooks-based Event Broker supports only the TeamForge-Jenkins integration to start with. As more supported integrations are in the pipeline, CollabNet recommends that you use the new Webhooks-based Event Broker to integrate Jenkins with TeamForge and migrate the existing Jenkins data from the EventQ’s database to the TeamForge database. For more information on how to migrate the existing Jenkins data from EventQ to TeamForge, see Migrate Existing Jenkins Data from EventQ to TeamForge.
In addition, a new version of the CollabNet Jenkins integration plugin, v2.0.6, is also available, which if configured can notify either the native TeamForge Webhooks-based Event Broker or EventQ about the build data.
If you use native Webhooks-based Event Broker, the build information will not appear on the Activity Stream and the build related reports will not work. For this reason, if you want to have the Jenkins plugin notify EventQ (instead of the Webhooks-based Event Broker) about the build data, see Configuring Jenkins Adapter to notify EventQ.
Register Events, Publishers, and Subscribers in TeamForge Webhooks-based Event Broker
Before you configure the Jenkins integration plugin to notify TeamForge Webhooks-based Event Broker about the build data, you must register the Events, Publishers, and Subscribers in TeamForge Webhooks-based Event Broker.
TeamForge 18.3 supports registration of Events, Publishers, and Subscribers via the TeamForge Webhooks-based Event Broker REST API calls.
To register events, publishers, and subscribers, see:
For more information on TeamForge Webhooks-based Event Broker REST APIs, see TeamForge Webhooks Event Broker REST API Documentation.
SCM - Git/Gerrit/Subversion
TeamForge-Git Integration 18.3.6-2.14.16 was released on Oct 23, 2018. For more information, see release notes of vanilla Gerrit version v2.14.16.
Inline Editing of Source Files on Git Repositories without Code Review
You can inline-edit the source files on Git repositories for which code review is not enabled. Browse and open the file on the View tab, click Edit to modify the file on the File Editor and click Save.
Inline Editing of Source Files on Subversion Repositories
You can inline-edit the source files on Subversion repositories. Just browse and open the file from a repository on the View tab. Click Edit to modify the file on the File Editor and click Save.
Filter Commits in the Changes Tab
Though the Changes tab typically consists of a long list of commits, you can filter commits by log message, author or by the committer. Just click Filter and type a keyword to search the log message or type the author or commiter name and click Done. The commits would be filtered by the criteria you entered. You can clear the filter criteria anytime.
Find Files as You Type
With the new Find File feature, to quickly find a file in a repository, just type the keywords and the results are shown instantly as you type.
View Git Blame Prior to a Specific Change
You can now view Git blame prior to a particular change. Browse and view a file in a Git repository, select the Annotations check box and click the View Git blame icon.
View PDF Files
You can now view the PDF files in Code Browser.
View Images Stored in Git LFS
You can view the image files stored in Git LFS. Supported formats: GIF, JPEG, and PNG.
The existing download tab is now replaced with a new Download button, which appears next to the Edit button on the Code Browser. Click this button to download the raw source files.
Support for Multiple Git LFS Backends in Code Browser
Prior to this release, the Code Browser was only able to access LFS files that were stored on local file system (FS backend).
Bug Fixes in TeamForge-Git Integration 18.3.6-2.14.16
- Prevent server out of memory issue on an attempt to download a very large file.
- Fixed various JGit related resource leaks.
- Viewable text file size is limited to 5MB. Larger files have to be downloaded.
- Improved performance of code browser when viewing files.
- Do not allow deletion of TeamForge projects.
- Improved error messages that are displayed when multiple users save “Default Branch” or “Submit Type” settings at the same time.
For Gerrit related bug fixes, see Bug Fixes in Gerrit 2.14.16.
Install / Upgrade
The following baseline related site-option tokens are added in TeamForge 18.3.
The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server and the
REPORTS_DATABASE_PORTtoken have been deprecated.
- During TeamForge installation, the
REPORTS_DATABASE_PORTtoken should no longer be used to assign a separate port for datamart.
- If you have the TeamForge database and datamart running on separate PostgreSQL instances on the same server, create a dump of both the database and datamart and load them into the same PostgreSQL instance. For more information, see Create a single cluster for both Database and Datamart.
- During TeamForge installation, the