Change Package Support

AccuRev change package support can be turned on in Enterprise Sync by setting specific attributes in the AccuRev Data Source definition (see Creating a Data Source).

This support maps AccuRev change packages with Endevor elements which have a specific CCID value associated.

There are two configuration options in Enterprise Sync:

• You may want to associate files which are synchronized from Endevor to an AccuRev change package depending on the last action CCID in Endevor.

  Enterprise Sync supports this based on the following rules:

  • During an initial synchronization, Enterprise Sync does not assign the synchronized files to change packages. This feature is only supported for incremental synchronizations.
    Note: Before running an initial sync, make sure that the AccuRev schema definition is defined in such a way that the synchronization user is allowed to add files to the streams without enforcing the association to change package.

    When defining the change package triggers condition in your AccuRev schema you could, for example, explicitly exclude the AccuRev streams which are mapped in Enterprise Sync to Endevor stages:

    
  • If an AccuRev schema does not exist Enterprise Sync will generate a default schema.
    Note: If change packages are used in AccuRev, we recommend creating the appropriate schema with the required fields, queries and status rules before activating the change package support in Enterprise Sync.
  • If an AccuRev schema exists, but does not have the configured CCID field associated, then Enterprise Sync will add this field automatically to the schema.
  • During the synchronization Enterprise Sync detects the last action CCID associated to the Endevor element.
  • If no change package has been created for that target stream which has the CCID value associated, Enterprise Sync will create a new change package and will associate the file to that change package.
    Note: The corresponding change package depends on the target stream to avoid conflicts in parallel development scenarios. Endevor doesn't assure that different CCIDs have to be used if a file is changed in parallel in different Endevor stages. To avoid logical conflicts in AccuRev different change packages are used in such constellations.
  • If change packages already exist for that target stream which has the CCID value associated, then the file will be added to all those change packages.
    Note: normally only one change package will exist related to the target stream which has a specific CCID value associated. Anyhow, Enterprise Sync does not disallow additional manually created change packages with the same CCID value.
• You may want to associate the change package's CCID value to the Endevor elements for all files which are synchronized from AccuRev to Endevor.
  • If the user promotes files to a gated stream and AccuRev is configured to force a change package selection when promoting, then Enterprise Sync uses the CCID value which is associated to the change package and associates this CCID to all synchronized Endevor elements.
  • If more than one change package has been selected when promoting files, then Enterprise Sync uses the CCID value of the first selected change package.
    Note: Although AccuRev allows the association of several change packages when promoting files, Endevor does only support the association of one CCID value when adding an element to the repository. To avoid logical conflicts it would be best practice implementing an (organizational) rule and allowing only the association of one change package when promoting files.
  • If the user has selected a change package with an associated CCID value when promoting, the promote dialog in Enterprise Developer will protect the CCID field, because the change package's CCID value will be used. This value cannot be overridden by the promote user.