Create a baseline when you release or deliver a product or when you accomplish specific milestones in your project. Such a baseline includes key data that describes or helps identify the work items in the same state as it existed at the time of creation of the baseline.

What is a Baseline?

A Baseline in TeamForge represents an approved snapshot of selected configuration items from a given TeamForge project at a given point in time. For example, you can create a Baseline when you release or deliver a product or when you accomplish specific milestones in your project. Such a Baseline includes key data that describes or helps identify the work items in the same state as it existed at the time of creation of the Baseline. In other words, Baselines, once created, cannot be modified.

What is a Baseline Definition?

A Baseline Definition is a template that consists of a set of predefined filter criteria to accelerate baseline creation. Baseline definitions can also be modified from time to time to suit your changing requirements.

What is a Configuration Item?

A Configuration item is a project artifact that can be uniquely identified.

Typically, a Baseline in TeamForge can include the following configuration items:

  • Tracker Artifacts
  • Documents
  • Source Code Repositories (from Git/Subversion repositories, identified by Tags)
  • File Releases
  • Binaries (Nexus)

Is there a separate license for the Baseline tool in TeamForge?

Yes, Baseline has its own license in TeamForge. You must have both ALM and Baseline licenses to create and work with the Baseline tool in TeamForge. For more information, see TeamForge License.

What are the permissions associated with the Baseline tool?

Here’s a list of Baseline-specific permissions. You can set up site-wide, project-level or global roles in TeamForge with the following permissions.

  • CREATE/VIEW BASELINE

    Users with this permission can:

    • Create a new baseline definition
    • Create a new baseline
    • View baseline definitions and baselines
    • Send baselines for review
    • Approve baselines
    • Reject baselines
    • Search for baseline definitions and baselines
    • Compare baselines
  • VIEW ONLY

    Users with this permission can:

    • View baseline definitions and baselines
    • Search for baseline definitions and baselines
    • Compare baselines

How would you create a Baseline in TeamForge?

Baseline creation in TeamForge involves the following steps:

1. Create baseline definitions

You can create a baseline definition by defining the filter criteria for Tracker Artifacts, Documents, Source Code Repositories, File Releases, and Binaries. Baseline definitions can be used while creating the baseline. You can also edit a baseline definition at any point in time. For more information, see Create Baseline Definitions.

2. Create baselines

You can create a new baseline using an existing baseline definition or without a definition. Baselines become immutable after their creation. For more information, see Create Baselines.

3. Review baselines

You can review the baseline once it is created. During the review cycle, the baselines can either be approved or rejected. For more information, see Review Baselines.

4. Compare baselines

You can compare baselines after they are approved. TeamForge 18.2 supports comparison of two baselines at tracker level. For more information, see Compare Baselines.

How would I install Baseline?

Baseline services can be installed when you install TeamForge. It’s highly recommended that you install the TeamForge Baseline services on a separate server as the baselining process can consume considerable CPU and database resources. For more information, see Install TeamForge in a Distributed Setup.