Date: Fri, 29 Mar 2024 13:02:19 +0000 (GMT) Message-ID: <1912439853.665.1711717339843@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_664_1215791484.1711717339834" ------=_Part_664_1215791484.1711717339834 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
SQL Change Automation allows you to automate the process of depl= oying changes to a database with confidence. It provides a set of PowerShell cmdlets that can valid= ate the project and run tSQLt tests before deploying the changes to differ= ent environments.
It also provides a set of add-ons = for continuous integration and continuous deployment servers, such as&= nbsp;Team Foundation Serve= r, Azure DevOps (former= ly VSTS, Visual Studio Team Services), Octopus Deploy, TeamC= ity, Bamboo and Jenkins.
Broadly speaking there are two parts to the process of deploying changes= . First the project is validated and a deployment package is produced - thi= s process is known as the build. This is explained in continuous integration.
The second part can be considered the release step. This takes the deplo= yment package produced by the build step and deploys it to the target envir= onment. This is explained in automated deployments.
Unless otherwise stated, all automation documentation supports both SQL Change Automation projects and SQL Sourc= e Control projects