Using the command line

All SQL CI command line switch names are case insensitive. The switch values are case sensitive. 

There's no restriction on the number of switches you can use or the order in which you use them.

Switches can be preceded by a forward slash '/' or two dashes '--'.

The SQL CI command line supports four steps that perform different continuous integration tasks. The steps are:

  1. Build - validates the SQL creation scripts and places them in a NuGet package. You can also send schema information to DLM Dashboard.
    See Using the build command
  2. Test - generates test data using SQL Data Generator and runs tSQLt tests against the NuGet package, such as static analysis, unit or integration tests. Results are output in JUnit XML format.
    See Using the test command
  3. Sync - updates the existing database with the latest version in source control.
    See Using the sync command
  4. Publish - publishes the NuGet package to a NuGet feed, ready for deployment.
    See Using the publish command

The test, sync and publish steps use the NuGet package created during the build step. These three steps are optional, but if you want to use them you must complete the build step first. 

There's also a command to activate your DLM Automation Suite license without having to configure a build, test or sync step.
See Using the activate command

Didn't find what you were looking for?