Creating a baseline

Creating a baseline for each Integration Testing and System Testing build enables testers and developers to refer to the set of changes that were used to create the build.

Create a baseline for all projects in the same release and purpose. For example, create a baseline for each Integration Testing build using all Integration Testing projects for that release.

You have probably updated the integration or system testing projects, dealt with conflicts, and built your products. You are now ready to create a baseline to save a copy of this build for future reference. When you create the baseline, you can publish it to make changes available to developers immediately. Alternatively, you can wait to publish the baseline after the build has had more testing.

Procedure

  1. Right-click over a project hierarchy or project grouping and select Create Baseline.

    You can create a baseline from a build management project grouping or from a project that is static or is a build management project.

    Note: When you create a baseline, you choose a list of projects to be included in the baseline. Be sure to include all related projects in your baseline so that you have a complete set for reference.
  2. In the Create Baseline dialog box, modify the properties of the baseline, as required.
    • Type a name in the Name field.

      This is the name of a baseline. It uniquely identifies this baseline within this database. By default, Rational® Synergy names baselines with the creation date; for example, 20090309 stands for March 9 2009. However, you can modify it. The following are restricted characters and should not be used in the name: / \ ' " : ? * [ ] @ - #

      If you are creating baselines in more than one database and you are using Rational Change to generate reports on the builds, use the same baseline name in each of the databases. Consistent naming allows you to generate a build report that has a related baseline in more than one database.

      The Name field is a required field.

    • Confirm that your release is correct.

      A release is a property that identifies a baseline that is specific to a particular release.

    • Confirm that your purpose is correct.

      A project purpose defines what the project is used for, for example, Integration Testing. The process rules use the purpose of the baseline to select the appropriate baseline during an update operation.

    • Optionally, you can set the build identifier by typing it in the Build field.

      The build property shows the build identifier (letters, numbers, or combination) associated with a baseline. The build identifier can contain a maximum of 64 characters.

      If you are creating baselines in more than one database and you are using Rational Change to generate reports on the builds, use the same baseline build identifier in each of the databases. Consistent naming allows you to generate a build report that has a related baseline in more than one database.

    • Type a description in the Description field to describe the baseline you are creating.
  3. Change the projects included in the baseline.

    If the Always include all subprojects regardless of release option is set in the Create Baseline action in the Options dialog box, then all projects for a project hierarchy, regardless of the release value, are available. If this option is not set, all prep subprojects are used. Only the static subprojects with a component that matches that of the top-level project are used.

    See Changing baseline creation options for details on setting this option.

    1. To add individual projects, click the Add Project button.

      The Select Project dialog box is displayed, which works the same as the Query dialog box. By default, projects displayed in the selection set field based on the release and purpose for the project, for example, toolkit/2.0 and System Testing. Additionally, you can define a query to find the project that you want to add to the baseline.

    2. To add all projects from a project grouping, click the Add Project Grouping button.

      The Select Project Grouping dialog box is displayed, which works the same as the Query dialog box. Adding a project grouping enables you to add projects associated with a project grouping, which is helpful if you are creating an incremental baseline. Additionally, you can define a query to find the project grouping that you want to add to the baseline.

    3. To add all projects from an existing baseline, click the Add Baseline button.

      The Select Baseline dialog box is displayed, which works the same as the Query dialog box. Adding a baseline enables you to add the projects associated with a baseline, which is helpful if you are creating an incremental baseline. Additionally, you can define a query to find the baseline that you want to add.

    4. Click OK.
  4. Publish the baseline to developers upon creation.

    If you are creating a test baseline for limited availability, skip this step and proceed to 5.

    This option is cleared by default. Set it. As soon as you publish the baseline, developers can update their projects to bring in the most recent changes from the baseline.

  5. Create the baseline by clicking OK.
  6. Release the baseline and all objects in the baseline upon creation, if appropriate.

    This option is cleared by default.

    This option is useful when creating the final baseline for a release because it saves the step of releasing the baseline after it is created.

  7. Click Preview Versions to preview the version template to be used for all projects, subprojects, and products created during baseline creation.
    1. In the Preview Versions dialog box, change, remove, and add version template keywords. Type directly in the Version Template field. You can add new keywords by clicking Add Keyword icon.

      The default template is defined in the Options dialog box, which is described in Changing baseline creation options.

    2. If you changed the version template and want to view all project and product versions in the baseline with the changes, click Preview.
    3. Save the settings to use when creating a baseline in the future by clicking .

      The version template is saved as the default.

    4. Click OK to save changes.
  8. Create the baseline by clicking OK.

Feedback