Page History

...

Switching versioning system

Anchor
versioning-system versioning-system

From In Blueriq 12.9, a new versioning system has been introduced. When installing Blueriq our , the old versioning system will be used to out of the box, this meaning . This means that Blueriq will use the Repository.sdf as the datasource for version management., containing all Blueriq repositories.

The new way of working separates out the history data from the working revisions, referred to as workspaces. To enable the new versioning system feature , simply remove the datasource configuration from the studio section of the config file for Blueriq Studio (StudioService.exe.config).

<configuration>
  <studio>
    ...
	<datasource location="../Repository/Repository.sdf" printqueries="false"/>

    <workspace-datasource host="localhost" port="5432" username="xxx" password="xxx" defaultdatabase="databaseX" database="databaseY" printqueries="false"/>
    <history-server basepath="http://localhost:1339/"/>
    ...
  </studio>
</configuration>

Remove the <datasource .../> element from this file, so that the <workspace-datasource .../> and <history-server .../>  elements will be used by the Studio. These configurations should have been configured correctly during the installation of the Studio, but can be changed accordingly if needed.

<configuration>
  <studio>
    ...

    <workspace-datasource host="localhost" port="5432" username="xxx" password="xxx" defaultdatabase="databaseX" database="databaseY" printqueries="false"/>
    <history-server basepath="http://localhost:1339/"/>
    ...
  </studio>
</configuration>

When the datasource configuration is removed Save the file and restart the Studio service; after the restart that the new versioning system will be enabled. 

Commit hook

The commit hook is a feature that sends an HTTP request to a configured endpoint whenever a commit is performed from within studio. This allows you to create buildpipelines that get triggered from Blueriq.

...