Published 15 May 2014
SQL Automation Pack v1.1.x.x releases contain a rewritten version of SQL CI which is not compatible with 1.0.x.x versions. If you're upgrading from a 1.0.x.x version, you must reconfigure your existing SQL CI build steps after installation.
Follow the configuration instructions for the SQL Automation Pack version you're upgrading to and the CI system you're using.
Upgrading from SQL Automation Pack 1.0.x.x to 1.1.x.x and later
Do not upgrade to SQL Automation Pack v188.8.131.52 because the MSBuild scripts are not supported in that release. You should upgrade to v184.108.40.2065 or later. For more information on using the new scripts, see Using the SQL CI TFS MSBuild scripts in SQL Automation Pack.
The TeamCity plugin installation file in SQL Automation Pack v1.1.x.x is called sqlci-teamcity, so installing it won't overwrite the previous plugin called RedGateSQLServer. Your TeamCity projects will continue to use the Red Gate (SQL Server) runner type until you're ready to configure them to use the new runner types. For more information on installing the plugin and using the new build steps, see Using the SQL CI TeamCity plugin in SQL Automation Pack.
Do not use the MSBuild scripts in SQL Automation Pack v1.1.x.x and later. You must use the new sqlCI.exe command line build steps instead. For more information, see:
- Database CI and automated deployment with Jenkins: a step by step tutorial - this blog post describes how to configure Jenkins using the new SQL CI commands.
- Using the sqlCI.exe command line in SQL Automation Pack v1.1 and later
Other CI systems
Do not use the MSBuild scripts in SQL Automation Pack v1.1.x.x and later. You must do one of the following:
- reconfigure your CI system to use the new sqlCI.exe command line build steps. For more information, see Using the sqlCI.exe command line in SQL Automation Pack v1.1 and later.
- use the build scripts available in SQL Automation Pack v220.127.116.11. See Download old versions of products.