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.
Each project can have one or more source code repositories. Before you can create a source code repository, a site administrator must first add one or more SCM servers to the Digital.ai TeamForge environment.
You can customize your reports by modifying the parameters in config.ini file. For example, some reports require a particular data source such as datamart and some require a particular license type such as ALM.
EventQ is no longer supported and is completely removed from TeamForge starting from TeamForge 20.0. If you have been using EventQ on your site, you must consider a few things when you upgrade to TeamForge 20.0 or later.
This section provides solutions to common issues with TeamForge-Binary integrations.
These are some of the frequently asked questions on Review Board.
Browse TeamForge to find the code you want to work on, then check out the code.
External public Git repositories can now be imported into TeamForge from the Code Browser UI.
The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings.
Memcached caches Subversion (SVN) authentication and authorization information and serves the mod_authnz_ctf module's authentication and authorization requests thereby reducing the number of SOAP calls, which in turn results in less load on the TeamForge Application Server.
Once you have your Nexus server set up, install the TeamForge-Nexus integration plugin.
Distributed setup with TeamForge, Database (including Datamart), Review Board, SCM (Subversion and Git), Code Search and Baseline installed on separate servers.
You can install TeamForge with its database installed separately on an external PostgreSQL server such as AWS RDS/Aurora.
Distributed setup with TeamForge and Oracle Database (including Datamart) 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.
You can make it easy for project members to use a wide variety of applications and sites from within TeamForge.
Post-submit webhooks lets you integrate TeamForge with other heterogeneous applications. Speaking of TeamForge trackers, post-submit webhooks are meant for publishing TeamForge tracker event messages (for example, artifact create or update event messages) to one or more subscriber applications such as Jira. The subscriber of the TeamForge post-submit events could be any application that supports webhooks.
Generate a report to get a snapshot of what is going on in a project. You can generate reports on data stored in both TeamForge's production (operational) database or datamart. Datamart, also known as the Reporting database, is build by extracting, transforming and loading (ETL) TeamForge's production data to a separate database (datamart) at regular intervals.
A Tracker is a collection of related artifacts that describe work to be done or issues to be resolved. Every project should have one or more trackers. When you start a tracker, you decide which fields will be used, who will use them, and how they will use them.
Change log of site-options.conf tokens.
When you purchase a TeamForge license, you get the right to assign licenses to a specified number of users.
Installing TeamForge in a Load Balancing setup ensures distribution of processing load between multiple servers. The HAProxy Server hosts the HAProxy services that are required for the load balancing function.
The Digital.ai TeamForge Maven Deploy Plugin can be configured to post binary artifact deployment information to TeamForge via the Webhooks-based Event Broker (WEBR) for end-to-end traceability.
Use the host:SERVICES and the host:PUBLIC_FQDN tokens to define the services and domain names of your TeamForge site respectively. You can also have unique service-specific FQDNs for services such as Subversion, Git, mail, Codesearch and so on.
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.
A TOPIC event type within the TeamForge Webhooks-based Event Broker is called as a Post-Submit event in TeamForge. The message of this event type is delivered to all the subscription endpoints.
If you have been updating your tracker artifacts both via the UI and CLI/SOAP, you may optionally run the `update_artifact_textflex_carriage_return.py` script to fix the inconsistent CRLF characters that were found to exist in the text flex field data.
You can upgrade TeamForge on new hardware in a distributed multi-host setup.
You can upgrade TeamForge on new hardware with all services on a single server.
You can upgrade TeamForge on the same hardware with all services on a single server.
You can upgrade TeamForge on the same hardware in a distributed multi-host setup.
Distributed setup with TeamForge, Oracle Database (including Datamart) and EventQ installed on separate servers.
With the new TeamForge Identity Management built on OpenID Connect (OIDC) and OAuth 2.0 authorization frameworks, TeamForge can now act as an ID Provider (IdP). As an IdP, TeamForge can authorize a third-party client application to obtain limited access to its services either on behalf of a Resource Owner (user) or on behalf of the client application itself.
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.