Rebuilding without a baseline

When you create a baseline, you communicate the added, removed, or excluded tasks to your team through the published baselines. For example, if you exclude a task, team members know that a task was excluded when they update their projects and get the new baseline.

Sometimes you are unable to create a baseline because, for example, the application might not build or the smoke test has failed. You must communicate with your team differently.

Now the build methodology is different from that given in the previous operations. Because you cannot build successfully, developers must test and fix before you can create a baseline. Notify developers that the build is broken and they must test and fix their completed tasks.

Procedure

  1. Developers right-click over the Integration Testing project grouping and select Copy All Tasks.

    This enables developers to obtain the latest tasks.

  2. Developers paste the tasks to their appropriate project grouping.

    Projects might contain many of the same tasks that are in the Integration Testing project grouping, but Rational® Synergy only pastes the tasks that are not in a developer project grouping.

  3. Developers test and fix tasks, informing you when tasks are completed.
  4. Manually add the completed tasks to the Integration Testing project grouping. (See Performing a rebuild.)
  5. Rebuild your product.

    This might fix the build problems; however, sometimes teams must go through many test and fix iterations before they can get a successful build.

  6. Once you build successfully and the build meets your quality standards, you can create a snapshot of the build.

Feedback