Adding a new project to an existing hierarchy

Steps 1a and 1b are necessary if a developer creates the project to be added to your existing hierarchy. Developers performing this operation need access to the component_developer role.

Procedure

  1. Be sure that developers complete the following tasks.
    1. Developer must complete their current tasks.
    2. Developers must check in their new projects.
  2. Copy an integration testing project from the project you checked in.

    Be sure to set the version, purpose, platform, and release.

  3. Add the new integration testing project to the integration testing project hierarchy.

    If the developer already added the project to a directory in the hierarchy and checked in that directory, update the integration testing project hierarchy. The update ensures that Rational® Synergy selects the new directory and includes the new project. Update is described in Updating the build management project hierarchy.

    Alternatively, if the developer did not add the new project to the hierarchy, add the project to the integration testing project hierarchy. (This operation is described in Adding an existing project to your hierarchy.) Additionally, create a task, then complete the task when the change is complete.

    If you have empty directory entries in your new project, some objects probably are not associated with a task for this release.

  4. Create an external project, if needed. Add one build management project for integration and one for system testing project.

    This operation is discussed in Creating an external project.

  5. Create versions for parallel platforms, if needed. Add one for integration and one for system testing project.

    This operation is discussed in Setting up platforms.

  6. If the new project applies to multiple releases, create parallel release versions of it. Add one for integration and one for system testing project.

    This operation is discussed in Setting up parallel releases.

  7. Change the makefiles, the build process, and all automated jobs to reflect the changes you have made.
  8. Complete any tasks you have used for restructuring.
  9. See Publishing a baseline to developers.
  10. Update your integration testing project hierarchy, rebuild your application, then run your test suite.
  11. Create another baseline.
  12. Create a corresponding system testing project for each new integration testing project.

    This operation is discussed in Creating the system testing projects.

  13. Update your system testing project hierarchy, rebuild your application, then run your test suite.
  14. Perform system testing.
    Note: Complete this process for each platform, checking out integration and system testing project for each platform.
Feedback