Back up and Restore TeamForge
Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site.
Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site.
You can use the checkout command to check out the code from Subversion or GIT repository.
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.
You can create a tracker artifact whenever you need to report and track a bug, feature request, support request, or other type of issue. You can also create a tracker artifact without logging into TeamForge just by sending an email to the tracker.
Updating the information in tracker artifacts is one important way that project members can work together effectively.
You can publish the output of your project to selected audiences as packages and releases.
The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings.
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.
Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.
Your My Workspace is a personal workspace that offers a handful of configurable widgets such as My Recent Projects, My Recent Repositories, Git Code Reviews, Project News and so on. You can use these widgets to view recent projects, recent repositories, recent commits, items assigned to you (TeamForge artifacts and document reviews), Git code reviews, project news, reports and more.
Queue type events are provided within the TeamForge Webhooks-based Event Broker to support client server processing and http based load balancing. It provides a robust mechanism for invoking jobs asynchronously and receiving the response through callbacks.
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.
The TeamForge Webhooks-based Event Broker v4 engine provides powerful scripting using JavaScript and custom JSON filtering capabilities that provide customization capability to products through webhooks.
Git Large File Storage (LFS) is a Git extension for versioning large files. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a separate server (typically a remote server).
Create pre-submit webhooks to enforce business rules on tracker artifacts and post-submit webhooks to deliver (custom-formatted) event messages to other tools. These webhooks are triggered when certain tracker events occur such as artifact create, update, move, clone or delete. You must have Project Admin permissions to set up pre-submit and post-submit webhooks.
Change log of site-options.conf tokens.
A SYNC event type within the TeamForge Webhooks-based Event Broker is called as a Pre-Submit event in TeamForge. Only one subscription is allowed for this event type.
An important aspect of the end-to-end development lifecycle is the creation and storage of software packages that are often binary artifacts. In the Java world, these are usually reusable jars that are used by other projects. Binary artifact repository managers are software systems that manage, version, and store binary artifacts. Example of such repository manager is Sonatype Nexus.
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.
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-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.
Use these instructions to upgrade Review Board to a latest build.
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.