An instance can have multiple peer instances but only one parent instance.

About this task

The parent instance is the only instance you can pull changes from and push changes to.

The parent instance must be on the same release family as the local instance. For example, a development instance on the Geneva release family must have a parent instance also on the Geneva release family. If you select a parent from a different release family, the Team Development dashboard displays an error message and prevents you from pulling changes and reconciling. If you select a parent from a different patch release, the dashboard displays a warning message but allows you to pull changes and reconcile.

Do not use Team Development with production or test instances.
  • Do not use a test or production instance as the parent instance in Team Development.
  • Do not make any instance the parent of a production instance.
  • Production instances should never have a parent.
When you back out a change on a Team Development instance, it backs out the change all the way back down the chain, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

Procedure

  1. Navigate to All > Team Development > Team Dashboard.
  2. If you defined a new remote instance in step 2, repeat step 1 through step 2 and select the remote instance you defined.

    The system initiates a reconcile, which compares the local instance to the parent. It then generates the list of local changes and calculates the number of changes that are ready to pull from the parent. The reconcile also validates the instance versions.

  3. Pull all changes from the parent instance if both instances are in the same release family.
    Note: The parent instance is saved in the glide.apps.hub.current system property.