Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Blueriq version management helps you keep track of and provide control over changes to your models. Version Control Management (VCM) is the management of changes to projects. It ensures that multiple business engineers can make different changes without interfering with each others work, that there always is a releasable version of the project and that the project can be released, even if not all features have been implemented.

User roles may apply to version management, for instance privileges to create or modify branches.

Tip
Please refer to the Version management guide in the Blueriq Knowledge Base to learn more about version management.

Concepts

Include Page
Repository structure visual
Repository structure visual

Repository

Repository can be viewed upon as a sort of file folder where all your application development is stored.

If you are authorized to do so, you can create, edit and delete a repository. This can all be done from the navigation panel.

A repository has the following characteristics:

Property

Description

NameName of the repository, e.g. the functional name of your application
Initial branch typeThe branch type is optional and could be helpful for structuring your repository or for applying user roles.
Initial branchThe first branch, e.g. "Trunk"
Initial commit messageMessage to register the creation of the repository, e.g. "Create repository"

Branch

A branch is a version or duplication of a certain state of your application, for instance to be able to apply modifications to your application in an isolated environment or to isolate it as a release version. When creating a new repository an initial branch has to be created. 

Creating a new branch:

  • Is done when creating a repository
  • Can be done from the navigation panel, using the context menu (use the three dots or right click on a branch)
    • This duplicates the latest commit of the selected branch. Pending changes will not be available in the new branch.
  • Can be done from the commit history view, using the context menu (use the three dots or right click on a commit)
Branch typeOptionalNameName of the branch e.g. name of a feature, release indicationFunctional nameOptional, can be used in documentationDescriptionOptional

A branch has the following characteristics:

Property

Description

optionally has a branch type.


Branch type

You can define your own branch typesown branch types.  This This could be helpful for structuring your repository or for applying user roles.

Property

Description

NameName of the branch type e.g

.

"Development" or "Feature" or "Release"Functional nameOptional, can be used in documentationDescriptionOptional