Generate and Download Baseline Packages

Generate Baseline Package

Once an Baseline or a Project Baseline is approved, you can generate a Baseline Package out of it and download the package.

To create a Baseline package:

1. Log on to TeamForge and select a project from My Workspace.
2. Click Baselines from the Project Home menu.
3. Select (click) an approved Baseline or Project Baseline from the list of baselines.
4. Click Generate Package.

   

5. Type a name for the package.

6. Select one or more categories that the package must include.

   Note: The categories available to select are those included in the Baseline or Project Baseline. You cannot generate more than one package for the same category (or the same set of categories).

   

7. Click Generate. A package is generated and listed on the Packages tab.

   

For a baseline including configuration items with large volume of data, there would be a delay in generating the package. In such cases, a “Click to refresh” link is provided to refresh the status of the package being generated.

Known Issue: The Baseline service may go down during the baseline creation or the package generation process, which may obstruct subsequent baseline operations. Restart the Baseline service (teamforge stop -s teamforge-baseline and teamforge start -s teamforge-baseline) to restore baseline operations.

Download Baseline Package

Once you generate a baseline package, you can download it to extract the package contents or share it with stakeholders, if required.

To download the required package, click the Download icon. A TAR file will be downloaded to the location specified in the baseline configuration file.

View Baseline Package

Once you download a package, you can extract the downloaded TAR file and view its contents.

Example baseline package folder structure:

Every baseline package contains the following files:

• The index.html that shows the list of all Tracker Artifacts, Documents, File Releases, Source Code Repositories, and Binaries, if these are included in the Baseline or Project Baseline from which the package was generated.

• The JSON file for each configuration item included in the Baseline or Project Baseline from which the package was generated. Each JSON file contains the manifest fields and the response specific to that configuration item.

• The packageInfo JSON file that contains the package details such as package id, title, status, category selected during package generation, user name, package creation date, download path.

• A files folder that contains all the files attached to the configuration items included in the Baseline or Project Baseline from which the package was generated.