Using external reporting and OLAP tools, query the datamart directly and generate reports. The database schema diagrams provide the means to create advanced query scripts to extract required information from the datamart.
Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site.
As a baseline administrator, you can configure the custom attributes used in the baselines, configure the custom statuses, and manage workflow status transitions and field inclusions.
You can compare two Baselines created at two different points in time to know the differences. You can also compare the Baseline Definitions of two Baselines.
The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server has been deprecated in TeamForge 17.11.
Create a Baseline when you accomplish specific milestones in your project or when you release or deliver a product. You can create a Baseline from either a Baseline Definition or from the ground up.
A Project Baseline is a baseline created on a project at a given point in time. Once you have Project Baselines created, you can kick start new projects from Project Baselines and proceed from when and where the Project Baselines were created in the past. Project Baselines are typically created using Project Baseline Definitions, when you release or deliver a product. You can create as many Project Baselines as required.
A Baseline Definition is the filter criteria that is used to create a Baseline from a set of selected configuration items such as Tracker Artifacts, Documents, Source Code Repositories (only Git and Subversion are supported), File Releases, and Binaries (only Nexus binaries are supported) in a given TeamForge project.
You can edit an existing Baseline Definition to add more filter criteria or modify the existing fields and filter criteria.
You can edit the existing fields in a Baseline as long as the Baseline is in open status. A Baseline cannot be edited after it is approved or rejected.
These are some of the frequently asked questions on the installation, upgrade, and site admin related activities in TeamForge.
Distributed setup with TeamForge, Database (including Datamart), Review Board, SCM (Subversion and Git), Code Search and Baseline installed on separate servers.
This page walks you through the installation procedure for TeamForge Webhooks-based Event Broker (WEBR).
Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.
Plan your installation or upgrade setup, hardware and software requirements and so on before you begin.
A Baseline or a Project Baseline, once created can be reviewed. During the review cycle, the Baseline or the Project Baseline undergoes various status transitions as defined by the Baseline Administrator.
Change log of site-options.conf tokens.
Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code.
What is a Baseline Definition?
Here's a list of TeamForge `site-options.conf` tokens and configuration information.
TeamForge Webhooks-based Event Broker is a webhook driven integration broker, delivered as a free technical microservice along with TeamForge. It is a replacement for the event brokering aspects of the now deprecated EventQ product.
The TeamForge Webhooks-based Event Broker related settings are discussed in this page.
TeamForge Webhooks-based Event Broker supports TeamForge—Jenkins integration. Jenkins integration plugin is used to integrate TeamForge with Jenkins using TeamForge Webhooks-based Event Broker.
TeamForge Webhooks-based Event Broker supports TeamForge-JIRA integration. A new JIRA integration plugin version 1.1 is used to integrate TeamForge with JIRA using the TeamForge Webhooks-based Event Broker.
TeamForge's native Webhooks-based Event Broker replaces EventQ as the default event broker to support TeamForge integration with TestLink. EventQ-based TeamForge—Testlink integration is no longer supported.
Use the teamforge.py script to deploy and undeploy services, start and stop services, verify the status of services, verify the application environment, bootstrap or migrate data, back up and restore data and do much more.
For Subversion and Git repositories, you have the option to use the TeamForge code browser which is turned on by default while integrating the source code server.