|February 22, 2019|
|May 16, 2019|
|August 5, 2019|
Here’s a list of what’s new with the TeamForge Baseline feature.
Create Projects from Project Baselines
Once you have Project Baselines created, you can kick start new projects from project baselines and proceed from when and where the Project Baseline was created in the past.
Use one of the following two pages to create projects from project baselines:
- View Project Baseline Page
Note: If you are a Site Administrator, see Create and Manage Projects to create a project from the Create New Project page.
Include Multiple Baseline Definitions Within Baseline Definitions and Project Baseline Definitions
A Baseline Definition created in a TeamForge project can now include one or more Baseline Definitions from within the same project, in which case the Baseline Definition would be derived as a union of the native filter conditions as defined in the Baseline Definition and the filter conditions of the selected Baseline Definitions.
Similarly, a Project Baseline Definition created in a TeamForge project can include one or more Baseline Definitions from the same project, in which case the Project Baseline Definition would be derived as a union of the native filter conditions as defined in the project Baseline Definition and the filter conditions of the selected Baseline Definitions.
A new field Include Definitions has been added in the Create Definition and Project Baseline Definition pages to enable you include multiple Baseline Definitions.
Include External Baselines
When you create a Baseline or a Baseline Definition or a Project Baseline Definition in a TeamForge project, you can include one or more approved Baselines or Project Baselines from other TeamForge projects. The baselines included from other projects are referred to as “External Baselines”.
For more information, see:s
Generate Baseline Packages
You can now generate a Baseline Package from an approved Baseline or a Project Baseline. You can also download and share the package with relevant stakeholders. For more information, see Generate and Download Baseline Packages.
Create Baseline Definitions from the Definitions List Page
You can monitor or unmonitor a Baseline or a Project Baseline. By default, users who create a Baseline or a Project Baseline can immediately start monitoring it.
Email notifications are sent to users that monitor a Baseline or Project Baseline when:
- the baseline is updated
- a package is generated for the baseline
- comments are added to the baseline
Associations Between Baselines and TeamForge Objects
Once you create a Baseline or a Project Baseline, TeamForge objects (configuration items) included in the baseline are associated with the baseline for traceability. TeamForge 19.0 supports baseline association with the TeamForge objects such as Trackers, Documents, and File Releases.
The new Baselines tab, added to Tracker Artifacts, Documents, and File Releases, shows the baseline or the list of baselines with which the TeamForge object is associated. Click the baseline ID to view the associated baseline.
For more information, see:
- View a Baseline from View Artifact Page
- View a Baseline from Document Details Page
- View a Baseline from View Release Page
Refresh Baseline Status and Package Status
For a baseline including configuration items with large volume of data, there would be a delay until the baseline is created or the package is generated. In such cases, a “Click to refresh” link is provided to refresh the status of the baseline being created or the package being generated.
Known Issue: The Baseline service may go down during the baseline creation or the package generation process, which may obstruct subsequent baseline operations. Restart the Baseline service (
teamforge stop -s teamforge-baseline and
teamforge start -s teamforge-baseline) to restore baseline operations.
TeamForge-Nexus 3 Integration
TeamForge 19.0 supports Nexus 3 integration. For more information, see How to integrate Nexus with TeamForge?
TeamForge Webhooks-based Event Broker
From TeamForge 19.0, TeamForge Webhooks-based Event Broker supports TeamForge-JIRA integration in addition to TeamForge-Jenkins integration (supported from TeamForge 18.3).
TeamForge-JIRA Integration Using the TeamForge Webhooks-based Event Broker
EventQ-based TeamForge-JIRA integration is no longer supported. A new TeamForge-JIRA integration plugin version 1.0 is available, which you can configure to notify JIRA issues (work items) to TeamForge via the TeamForge Webhooks-based Event Broker. For more information on configuring JIRA adapter to notify TeamForge, see Configure JIRA Integration Plugin to Notify the Webhooks-based Event Broker.
Once you’ve configured the new TeamForge-JIRA integration plugin, you must migrate any existing JIRA data from the EventQ database to TeamForge database. For more information on how to migrate the existing JIRA data from EventQ to TeamForge, see Migrate Existing JIRA Data from EventQ to TeamForge.
Register Events, Publishers, and Subscribers in TeamForge Webhooks-based Event Broker
Before configuring Jenkins or JIRA integration plugin to notify TeamForge Webhooks-based Event Broker, you must have the Webhook URL, which is generated when registering the event, the publisher and the subscriber in TeamForge Webhooks-based Event Broker.
To register events, publishers, and subscribers in TeamForge Webhooks-based Event broker, run the script
create_webhook_event.py, which is newly added in TeamForge 19.0.
Enhanced Add New Tool Page (Integrate / Link External Application)
As a TeamForge Project Administrator, in addition to adding integrated applications to projects, you can now link external applications to projects using the Linked Application option from the Select Tool Type drop-down list (Project Admin > Tools > Add New Tool page).
GitAgile™—Enterprise Version Control
TeamForge-Git Integration 19.0.9-2.15.10 was released on Feb 12, 2019, which is based on vanilla Gerrit version v2.15.10. Read more to know what’s new.
Replicate Multiple Repositories with Ease
Setting up replication one-by-one for a large number of repositories can be time consuming. You now have an exclusive REPLICAS tab from where you can set up replication for multiple repositories in one go.
The REPLICAS tab lists all the available repositories and replica servers in a tabular format. Simply select or clear the check boxes to enable or disable repository replication on the available replica servers.
Tab-level Contextual URLs for Sharing
Every tab on a TeamForge SCM page can now be identified with a unique URL, which if copied and shared with others, can take them to the same page with the same tab selected.
Internal Code Browser: Code Review Process Enhancements
Check Boxes to Mark Files as Reviewed: With open code reviews, a check box is added to all the files listed in the Files tab. This check box is selected to mark files as reviewed when you open a file for review and close the file. You may also manually select or clear the check box to mark a file as reviewed or not respectively.
Reply to Comments During Code Reviews: You can now reply to comments added to files during code reviews. In other words, comments can now become a conversation/discussion during code reviews. You can also quote comments while replying to other’s comments and mark comments as Done.
View the Entire Diff: Instead of reviewing files one-by-one, you can click the view the entire diff link on the Files tab and review the entire diff on the same page.
Private and WIP Reviews: You can now mark code review as
Work In Progress(WIP), which comes in handy when you want to collaborate with others in private on experimental changes. With this enhancement, the
Draftoption, which is used to mark code reviews as draft, is no longer available.
Multiple Tags for a Single Commit: Unlike in the past when a commit can have only one tag (new tag overwrites the old tag, if any), you can now associate multiple tags, each with its own note, pointing to a single commit.
Bug Fixes in TeamForge-Git Integration 19.0.9-2.15.10
- When a Git replica was deleted, the details of the deleted replicas were not shown in the Replication Command History section. This was fixed.
- PDF files, when downloaded, were not downloaded. They were opened on the browser instead. This was fixed.
Duplicate Gerrit groups were created whenever a Gerrit group was added to a Gerrit project that was replicated on replica servers. This was fixed.
Fixed an issue that prevented Git/Gerrit from using the installed Java 1.8.
gerrit.system.logfile has been enhanced to log errors that occur when assigning permissions to users fail.
Pushing commits to replica servers has been blocked.
- When the
DATABASE_SSLtoken is set to ON, TeamForge provision failed during the bootstrap of the reporting database. This issue was fixed.
- Unlike in the past, some of the errors that occured when the TeamForge-Gerrit synchronization fails on locked TeamForge projects are no longer logged.
- TeamForge 19.0 supports:
- PostgreSQL 11.1
- RHEL/CentOS 7.6
- TeamForge 19.0 supports PostgreSQL 11.1. If you are upgrading from TeamForge 17.1 or earlier versions, PostgreSQL 9.2/9.3 data cannot be migrated automatically. You must manually create a database dump and reload the dump while upgrading to TeamForge 19.0. For more information, see TeamForge 19.0 upgrade instructions.
- EventQ is not installed by default when you install TeamForge 19.0. However:
- You can install EventQ separately, if required.
- If you have been using EventQ in the past, you can continue to use EventQ post upgrade to TeamForge 19.0. In this case, there is no need to upgrade EventQ in case you are upgrading from TeamForge 18.3 to TeamForge 19.0. For more information, see TeamForge 19.0 upgrade instructions. EventQ upgrade is required if and only if you are upgrading from TeamForge 18.2 or earlier to TeamForge 19.0.
- There is a set of new site option tokens added in TeamForge 19.0. Here’s the list of new and obsolete site option tokens in TeamForge 19.0.
Configure Your Site’s Settings
The System Tools > Configure Application page.
Limit the size of a single file attachment in Tracker Artifacts
A new site parameter, MAXIMUM SIZE FOR SINGLE FILE ATTACHMENT, is added (in the Tracker section) to set the size of a single file that can be attached to Tracker artifacts.
Speed up Mass Import process
A new site parameter, MASS IMPORT THREADS COUNT, is added (in the Tracker section) to increase the thread count for the Mass Import process. The default thread count is 1. Increase the thread count if you want to speed up the Mass Import process, but at the cost of increased CPU utilization.
Reactivate Deprecated EventQ Features
Some of the EventQ features such as the Activity Stream, EventQ based reports, and the Include Traceability check box (on the add/edit project tool page) are deprecated in TeamForge 19.0 by default. If you have been using EventQ earlier and willing to use EventQ post upgrade to TeamForge 19.0, you must use this new site parameter, ACTIVITY STREAM AND REPORTS, to enable the Activity Stream, EventQ reports, and the Include Traceability check box.
For more information, see Configure Your Site’s Settings.
teamforge reload Command
teamforge reload command comes in handy when you want to quickly bring up the site after modifying some of the frequently-used
site-opitons.conf tokens. Certain site-options.conf tokens, when modified, require stopping, deploying, restarting and initializing certain services. Instead of restarting the whole site, the
teamforge reload command, depending on the tokens modified, restarts only the services that need a restart, while keeping the site up for other services.
For more information, see teamforge reload.