🚀 Welcome to MDriven Learn –  MDriven is now on Discord!  Don’t miss the latest Release Notes.
Source control integration with MDriven
This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.

Continuous-integration automation

MDriven continuous integration (CI) describes automation of build, evolve, and deploy work. The documented automation steps are:

  1. Generate all code to ensure that the code maps to the model.
  2. Rebuild all so that assemblies are built before upload for CodeDress use.
  3. Upload to MDrivenServer to initiate evolve and the database operation.

The documented Visual Studio automation starts Visual Studio with the solution as a standard solution argument and supplies the model using MODELAUTOMATION="%MODELFILE%".

Before starting Visual Studio, the documented environment variables are MODELAUTOMATION_URL, MODELAUTOMATION_USER, and MODELAUTOMATION_PWD. The output-directory and output-file-path variables are documented as optional or overriding output settings.

Source control

The supplied documentation does not establish a supported workflow for storing, diffing, merging, or committing MDriven model files in Git, SVN, or another source-control system. Do not add repository-layout or merge-resolution instructions until those details are confirmed in MDriven documentation or by the product team.