Date: Thu, 28 Mar 2024 14:59:59 +0000 (GMT) Message-ID: <1944598291.425.1711637999832@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_424_922455199.1711637999826" ------=_Part_424_922455199.1711637999826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Creates a build artifact from the validated project produced by the Invo= ke-DatabaseBuild cmdlet.
New-DatabaseBuildArtifact [-InputObject] &=
lt;IProject> -PackageId <string> -PackageVersion <string> [-=
PackageDescription <string>] [-Documentation <SchemaDocumentation&=
gt;] [<CommonParameters>] |
The New-DatabaseBuildArtifact cmdlet takes a validated project from the = output of the Invoke-DatabaseBuild cmdlet and creates a build artifact. It = can also include the documentation for your database using the output of th= e New-DatabaseDocumentation cmdlet.
You can use the Export-DatabaseBuildArtifact cmdlet to export the build = artifact.
-InputObject <RedGate.Versi=
oning.Automation.Compare.Domain.Projects.IProject>
The output object of Invoke-DatabaseBuild cmdlet, which represents the v= alidated project.
Aliases | None |
Required? | true |
Position? | 0 |
Default Value | None |
Accept Pipeline Input | true (ByValue) |
Accept Wildcard Characters | false |
-Packa=
geId <System.String>
The unique identifier for the package you are creating.
This mustn't contain more than 100 characters and must be a valid NuGet = package identifier.
Aliases | None |
Required? | true |
Position? | named |
Default Value | None |
Accept Pipeline Input | false |
Accept Wildcard Characters | false |
-=
PackageVersion <System.String>
The version of the package. This must be in a valid NuGet version format= (eg 3.2.1, 3.2.1-beta1).
Aliases | None |
Required? | true |
Position? | named |
Default Value | None |
Accept Pipeline Input | false |
Accept Wildcard Characters | false |
The description of the package you are creating.
Aliases | None |
Required? | false |
Position? | named |
Default Value | None |
Accept Pipeline Input | false |
Accept Wildcard Characters | false |
-Documentation <=
RedGate.Versioning.Automation.Compare.Documentation.SchemaDocumentation>=
The documentation object created by New-DatabaseDocumentation to include= in the database package.
Aliases | None |
Required? | false |
Position? | named |
Default Value | None |
Accept Pipeline Input | false |
Accept Wildcard Characters | false |
<CommonPara=
meters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorActi= on, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see= http://technet.microsoft.com/en-us/libr= ary/hh847884.aspx.
The input type is the type of the objects that you can pipe to the cmdle= t.
The output object of Invoke-DatabaseBuild cmdlet, which = represents the validated project.
The output type is the type of the objects that the cmdlet emits.
|
This example shows how to use the New-DatabaseBuildArtifact cmdlet to cr= eate a build artifact from a validated SQL Change Automation project.
First the Invoke-DatabaseBuild cmdlet validates the project. Then the Ne= w-DatabaseBuildArtifact cmdlet creates the build artifact. Finally the Expo= rt-DatabaseBuildArtifact cmdlet exports the build artifact to file.
|
This example shows how to use the New-DatabaseBuildArtifact cmdlet to cr= eate a NuGet package from a validated SQL Source Control project.
First the Invoke-DatabaseBuild cmdlet validates the database schema. The= n the New-DatabaseBuildArtifact cmdlet creates the build artifact. Finally = the Export-DatabaseBuildArtifact cmdlet exports the build artifact to file.=
|
This example shows how to use the New-DatabaseBuildArtifact cmdlet to cr= eate a NuGet build artifact that also includes database documentation.
The documentation is created by the New-DatabaseDocumentation cmdlet.