25 docs tagged with "ctf_19.0"

Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site.

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.

This script creates an event, a publisher (with the Webhook URL), and a subscriber in TeamForge Webhooks-based Event Broker for a specified application.

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.

This section provides solutions to common issues with TeamForge-Binary integrations.

You can generate a downloadable package of physical project artifacts such as Tracker Artifacts, Documents, Source Code Repositories (only Git and Subversion are supported), File Releases, and Binaries (only Nexus binaries are supported) from an approved Baseline or a Project Baseline and share the package with your stakeholders.

Baseline

The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings.

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.

Plan your installation or upgrade setup, hardware and software requirements and so on before you begin.

Change log of site-options.conf tokens.

What is a Baseline Definition?

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.

Here's a list of TeamForge `site-options.conf` tokens and configuration information.

TeamForge Webhooks-based Event Broker supports TeamForge-JIRA integration. A new JIRA integration plugin version 1.2 is used to integrate TeamForge with JIRA using the TeamForge Webhooks-based Event Broker.

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.

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.

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.