Converting for developers

After the build manager convert projects to use process rules, developers must perform the following operations.

About this task

When developers are ready to start using process rules, they can convert their existing projects. If you are starting a new release, developers can copy new projects instead of converting their old ones.

To convert existing projects to use process rules, perform the following steps. (Before developers use this procedure, the build manager must have set up process rules for the current release. Refer to Converting for build managers.)

Procedure

  1. Use the Project Properties dialog box to change the release setting for each project. To change the release value for all projects in a hierarchy, perform the following steps.
    1. Right-click on the top-level project and select Properties.
    2. In the Project Properties dialog box, select the new release value in the Release list.

      If the project has subprojects, the release is changed on all subprojects automatically.

    3. Set the Purpose to Insulated Development, Collaborative Development, or Custom Development. If you use Custom Development, select your baseline. (See Selecting a new baseline.)
    4. Save the changes.
  2. Start a session from the command prompt.

    ccm start -h engine_host -d database_path -nogui

    After the session starts, the address (CCM_ADDR) is printed in your command window (Windows) or in the shell where you started the session (UNIX).

  3. Query for all process rules for the new release.

    Run a command on the selection set (query output).

    ccm query -type process_rule "release='new_release'"

    Where 'new_release' is the new release name.

  4. Specify that you want new projects to use process rules by default.

    ccm process_rule -modify -default @

  5. Exit the session.

    ccm stop


Feedback