The Versions tab provides a list of all the significant changes (ie commits) made to the model in the Model Datastore.
Source Control
The model artefacts are stored in a web based Git repository (Azure DevOps, Bitbucket, GitHub, AWS Code Commit, etc) (aka the Model Datastore).
A version reprenents a specific commit in the underlying Git repository. There is as such, a one to one relationship between a commit and version. Note: This A version is basically a commit but with a unique version number which allows for the commit to be better managed in the Model Catalogue.
However, the list of commits shown in the Model Catalogue is normally just a subset of the actual commits made in the Model Datastore. Providers typically choose to only publish the commits that the wish to make available to potential consumers. Most commits in the Git repository will never be published into the Model Catalogue. This allows providers to only publish commits that:
- meet certain their minimum quality control standards (eg reviewed, tested, etc).
- are significantly different from previous commits
- separate development and production versions of the model artefacts
Usage
Provider
Consumer
Similar to the other tabs, only providers can add/edit/delete versions. The button 
will prompt the providers to a pop up window to add versions. Providers can edit existing versions by clicking on the 
and the 
button will copy the guid of the version to the clipboard.
To delete a version simply click the 
button.
Adding a new version
Using the button 
, providers can add a new version to a model. In the Add New Version window the following parameters can be found.
...