Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Package Version Control Options

When you have set up a Package for Version Control, you gain access to a range of Version Control operations that can be performed on that Package, such as:

  • Open the dialog for working with baselines of the Package
  • Check-in and check-out single Packages or a selected hierarchy of Packages
  • Update Packages to the latest revision from the Version Control repository
  • Inspect the revision history or properties of the XMI file associated with a Package
  • Revert a Package to a previous revision
  • Compare the current model content of a Package, against the latest revision of the Package in Version Control
  • Import and export hierarchies of Packages (model branches) to and from the model, through the Version Control system
  • Synchronize the status of a Package, with the Version Control system

Access

Context Menu

Right-click on Version Controlled Package > Package Control

Options

Option

Action

See also

Check In Branch

Check-in Packages contained in the currently selected model branch (that is, the selected Package and all of its child Packages).

The 'Select Packages to Check In' dialog lists all Version Controlled Packages within that branch that are checked out to you; you can then select Packages in the displayed list, to be submitted for check-in.

You can also choose to keep the Packages checked-out after committing a new revision to Version Control.

Check In a Model Branch

Check Out Branch

Recursively check out all Packages contained within the currently selected model branch (that is, the selected Package and all of its child Packages) that are Version Controlled and checked-in.

Check Out a Model Branch

Check In

Commit a new revision of the currently selected Package to the Version Control repository and lock the Package against further editing.

Only available for Packages that you have checked-out yourself.

Check In a Package

Check Out

Synchronize the currently selected Package with the latest revision from the Version Control repository and unlock the Package to allow editing.

Only available for Packages that are not already checked-out (and whose associated Package file is not checked-out).

Check Out a Package

Undo Check Out

Restore the selected Package to the latest revision in the Version Control repository and lock the Package against further editing.

Undo Check Out of a Package

Put Latest

Commit a new revision of the currently selected Package to the Version Control system, while keeping the Package checked-out.

This is equivalent to checking a Package in and immediately checking it back out again.

Only available for Packages that you have checked-out yourself.

Get Latest

Synchronize the currently selected Package with the latest revision from the Version Control repository.

Available only for Packages that are checked in.

Update to the Latest Revision of Selected Package

Get All Latest

Updates all of the Version Controlled Packages in the project, to the latest revision retrieved from Version Control.

Only updates Packages that are currently checked in.

Once the latest revisions are retrieved, the system scans all the controlled Packages and fixes any missing cross-references by comparing the Package with its XMI 1.1 file.

If the cross-reference information in the XMI does not match the model, the system updates the model with the information from the XMI and records this update in the System Output window.

You can roll back such updates by selecting the entry in the System Output window and using the context menu option 'Rollback Update' (or 'Rollback Selected Updates' if multiple entries are selected).

  • Closing the model clears the entries in the System Output window
  • An entry in the System Output window is also cleared as and when you roll-back the update for it
Update to the Latest Revision of All Packages The System Output Window

Scan XMI and Reconcile Model

Scan the Package XMI files associated with each of the project's controlled Packages and restore any diagram objects or cross-references that are detected as missing from the project.

This function is useful in team environments where each user maintains their own private copy of the model database (that is, multiple private project files) and model updates are propagated through the use of controlled Packages. It provides no benefit when the model is hosted in a single shared database that is accessed by all team members.

Each controlled Package is compared with its associated XMI file and, if the cross-reference information in the model does not match the XMI, the system updates the model with the information from the XMI and records the update in the System Output window.

You can roll back such updates by right-clicking on the entry in the System Output window and selecting the 'Rollback Update' option (or 'Rollback Selected Updates' if multiple entries are selected).

Closing the model clears the entries in the System Output window; an entry in the window is also cleared as and when you roll-back the update for it.

This functionality is invoked automatically as part of the 'Get All Latest' operation.

When working in an environment that uses a Private Model deployment and your model contains a significant number of cross-Package references, it is recommended that you invoke 'Scan XMI and Reconcile Model' from time to time, following the re-importation of controlled Packages - for example, after using 'Get Latest' to update a number of Packages - or after performing a number of Package check-outs.

  • As a general rule, avoid running 'Scan XMI and Reconcile Model' while you have uncommitted changes in your model; generally, you:
         -  Check-out a number of Packages
         -  Invoke 'Scan XMI and Reconcile Model'
         -  Make your modifications
         -  Commit any outstanding changes before you check-out more
            Packages and run 'Scan XMI and Reconcile Model' again
http://sparxsystems.com/WhitePapers/Version_Control.pdf

File Properties

Display Version Control properties pertaining to the XMI export file associated with the currently selected Package; this also identifies who has checked out the Package.

File History

Display change history information for the currently selected Package.

Revert to or check-out a prior revision of the Package.

Review Package History

Compare with Controlled Version

Compare the currently selected Package with the latest revision of its associated XMI file retrieved from Version Control.

Add Branch to Version Control

Apply Version Control to all Packages within a selected model branch, in a single operation.

In this context, a model branch is a Package that is currently selected in the Browser window, and all of the Packages contained within it.

Apply Version Control To Branches

Export as Model Branch

Export a newly created model branch from your own private copy of a model.

Export Controlled Model Branch

Import a Model Branch

Retrieve a model branch and import it into either the source model or another model.

Import Controlled Model Branch

Get Package

Access Packages in the Version Control repository that are not currently available in your model.

Include Other Users' Packages

Re-synch Status With VC Provider

Update the Version Control status value recorded for the selected Package in the project to match the value reported by the Version Control provider, without performing an XMI import or export.

Use this function when the Package's Version Control status recorded in your project is out of synchrony with the Version Control status reported by your Version Control provider.

Resynchronize the Status of Version Controlled Packages

Version Control Settings

Display the 'Version Control Settings' dialog.

Version Control Settings

Notes

  • You set up Version Control using options from the project 'Version Control' submenu
  • If the selected Package is not under Version Control, a different set of options is available
  • If a Version Control configuration has not been defined for the model, no options for using Version Control are available, only the options for configuring Version Control

Learn more