SQL Automation Pack 1.1.0 release notes
Published 10 June 2014
184.108.40.2060 - June 23rd, 2014
This release contains a new version of SQL CI (v220.127.116.11). It provides improved support for LocalDB, and support for masked passwords in Smart Assembly and TFS log files.
If you have LocalDB installed, it'll be used by default during the build and test steps to recreate your database. You don't need to configure the /temporaryDatabaseServer option. If you don't have LocalDB installed, you'll need to enter a temporary server name.
There's also a new /runOnly option in the command line test step and in the Red Gate SQL CI Test runner for TeamCity. It allows you to specify a test class and test name to run, instead of running every test by default.
For more details, see Using the sqlCI.exe command line in SQL Automation Pack v1.1 and later.
Team Foundation Server passwords were visible in Smart Assembly and TFS log files in the previous SQL Automation Pack release. This issue is fixed in this release, so passwords are now masked.
For details of how to mask passwords in other CI servers, see:
Installing the SQL Automation Pack will force your machine to restart automatically by default. To stop this happening, turn off the check box at the bottom of the final installation page.
18.104.22.1685 - June 5th, 2014
This release contains a new version of SQL CI (v22.214.171.124).
Support for TFS MSBuild scripts
The MS Build scripts now support SQL CI v2.0. If you want to set up continuous integration with TFS, you can use the files in the tfs-scripts folder to build, test, synchronize and publish a NuGet package quickly and easily. For more information, see Using the SQL CI TFS MSBuild scripts in SQL Automation Pack.
- NAnt build scripts are not supported in this release.
- Installing the SQL Automation Pack will force your machine to restart automatically by default. To stop this happening, turn off the check box at the bottom of the final installation page
126.96.36.199 - May 16th, 2014
This release contains new versions of SQL CI (v188.8.131.52), the TeamCity plugin (v184.108.40.206), and SQL Doc (v220.127.116.11).
SQLvCI v2.0 supports four steps that let you build, test, synchronize and publish a NuGet package quickly and easily. The steps are:
- Build - creates and validates the SQL creation script used to generate the NuGet package.
- Test - generates test data using SQL Data Generator and runs tSQLt tests against the NuGet package. Results are output in JUnit XML format.
- Sync - updates the existing database server with the latest version in source control.
- Publish - publishes the NuGet package to a NuGet feed.
For more information, see Using the sqlCI.exe command line in SQL Automation Pack v1.1 and later.
The latest TeamCity plugin supports three of the new build steps in SQL CI v2.0. On the TeamCity Build Steps page, you can select new runner types:
- Red Gate SQL CI Build
- Red Gate SQL CI Test
- Red Gate SQL CI Sync
The new TeamCity plugin installation file is called sqlci-teamcity, so installing it won't overwrite the earlier plugin called RedGateSQLServer. Your TeamCity projects will continue using the Red Gate (SQL Server) runner type until you're ready to reconfigure them using the new runner types.
For more information on installing the plugin and using the new runners, see Using the SQL CI TeamCity plugin in SQL Automation Pack.
The latest plugin is compatible with TeamCity v7 and later.
SQL Doc has been updated to v3.0. For more information, see SQL Doc 3.0 release notes.
- SQLCI-116 Default output path contains illegal characters
SQLCI-122 Multi-word additional parameters truncated (/TIL:READ COMMITTED)
- SQLCI-153 CLR feature enabled by default on target server
- The Build Scripts automation tool is not supported in this release. For details of how to use this release with your CI system, see Upgrading.
- Installing the SQL Automation Pack will force your machine to restart automatically by default. To stop this happening, turn off the check box at the bottom of the final installation page.