Adding a new project to an existing hierarchy

About this task

Steps a and b below need to occur if a developer creates the new project to be added to your existing hierarchy. Developers performing this operation need to have the component_developer role set in Rational Synergy Classic.

Procedure

  1. Be sure that the developer does the following:
    1. The developer must complete his current task.
    2. The developer must check in his new project.
  2. Copy an integration testing project from the project you just 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 to ensure 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, you will need to add the project to the integration testing project hierarchy. (This operation is described in Adding an existing project to your hierarchy.) Additionally, you will need to create a task, then complete the task when the change is complete.

    If you get empty directory entries in your new project, it could be because some objects are not associated with a task for this release.

  4. Create an external project, if needed. Note that you need to 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. Note that you need to 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. Note that you need to 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 through 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 through your test suite.
  14. Perform system testing.
    Note: Complete this process for each platform, checking out integration and system testing project for each platform.

About this task

The following two bulleted items need to occur if a developer creates a new project to be added to your existing hierarchy.

Procedure

  1. Be sure that the developer does the following:
    1. The developer must complete his current task.
    2. The developer must check in his new project to the shared state.
  2. Change the work area path by turning off work area maintenance (because you cannot write to a developer’s personal work area).

    ccm work_area -nwa -project project_name-version

  3. Select the project’s work area and set the path to a build management work area location.

    ccm work_area -wa -setpath new_path -project project_name-version -r

  4. Check in the shared project to the integrate state.

    ccm checkin -c "comment" -state integrate -project project_name-version

  5. Copy an integration testing project from the project you just checked in.

    You will need to set the version and release. The purpose is set correctly by default.

    ccm co -to version -release release -project project_name-version

  6. Turn on work area maintenance again.

    ccm work_area -wa -project project_name-version

  7. 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 to ensure that Telelogic 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, you will need to add the project to the integration testing project hierarchy. (This operation is described in Adding an existing project to your hierarchy.) Additionally, you will need to create a task, then complete the task when the change is complete.

  8. Create an external project, if needed. Note that you need to add one for integration and one for system testing project.

    This operation is discussed in Creating an external project.

  9. Create versions for parallel platforms, if needed. Note that you need to add one for integration and one for system testing project.

    This operation is discussed in About building on parallel platforms.

  10. If the new project applies to multiple releases, create parallel release versions of it. Note that you need to add one for integration and one for system testing project.

    This operation is discussed in Setting up parallel releases.

  11. Change the makefiles, the build process, and all automated jobs to reflect the changes you have made.
  12. Complete any tasks you have used for restructuring.
  13. .
  14. Update your integration testing project hierarchy, rebuild your application, then run through your test suite.
  15. Create another baseline.
  16. Create a corresponding system testing project for each new integration testing project.

    This operation is discussed in Creating the system testing projects.

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

Feedback