Comments
Sort by recent activity
@Tianjiao_Li, wondering if thou might have any additional info regarding my last post's questions? / comments
@Tianjiao_Li, wondering if thou might have any additional info regarding my last post's questions?
That's good info, although a little vague. How do I set the "schema version" on the build artifact so dlm dashboard picks it up? And which bamboo variable do I set? Edit: I'm using octopus deploy now, but the release_version and package_version columns are not getting populated. What do I med to do within octopus deploy to populate them? / comments
That's good info, although a little vague. How do I set the "schema version" on the build artifact so dlm dashboard picks it up? And which bamboo variable do I set?Edit: I'm using octopus deploy no...
Excellent - and I love that you used extended properties for the metadata. / comments
Excellent - and I love that you used extended properties for the metadata.
How do these columns relate to DLM Dashboards "schema version"? And, is there a way to link into the Bamboo "Release Version"? I realize that's not fully a RG question... / comments
How do these columns relate to DLM Dashboards "schema version"? And, is there a way to link into the Bamboo "Release Version"? I realize that's not fully a RG question...
It's also not generated when deploying using MSBuild within the IDE. / comments
It's also not generated when deploying using MSBuild within the IDE.
Sergio answered the question, but for additional documentation, the schema snapshot will NOT get created when deploying using SSMS (ie TargetedDeploymentScript.sql). / comments
Sergio answered the question, but for additional documentation, the schema snapshot will NOT get created when deploying using SSMS (ie TargetedDeploymentScript.sql).
<Deleted - mistaken post> / comments
<Deleted - mistaken post>
Russell D said:
Hi Peter, this could be a problem with the syntax - can you share the command you're trying?
Russel - I put this code in the thread. Hoping you can shed some light on correct usage. / comments
Russell D said:
Hi Peter, this could be a problem with the syntax - can you share the command you're trying?
Russel - I put this code in the thread. Hoping you can shed some light on correct...
$ErrorActionPreference = "stop" #Input the build artifact nupkg file path $pathToBuildArtifact = "C:\Export\DatabaseBuild\SCAPOC.1.0.0.nupkg" #Input the path to export the release artifact to $exportPath = "C:\Export\DatabaseRelease\tmp" #try multiple targets $t1 = New-DatabaseConnection -ServerInstance "localhost" -Database "SCAPOC_UAT" $t2 = New-DatabaseConnection -ServerInstance "localhost" -Database "SCAPOC_PROD" #ERROR: To create a release for a SQL Change Automation project, the Target parameter must be a single Database #Connection. #Create and export a release artifact - based on 2 targets $releaseArtifact = New-DatabaseReleaseArtifact -Source $pathToBuildArtifact -Target @($t1, $t2) / comments
$ErrorActionPreference = "stop"#Input the build artifact nupkg file path$pathToBuildArtifact = "C:\Export\DatabaseBuild\SCAPOC.1.0.0.nupkg"#Input the path to export the release artifact to$exportPa...
# And here is the code that exported the build artifact $ErrorActionPreference = "stop" # Input path to SCA project file $pathToProjectFile = "C:\Users\peter\Documents\IncommSVN_PPD\SCAPOC\SCAPOC\SCAPOC\SCAPOC.sqlproj" #validate the project by building $validatedProject = $pathToProjectFile | Invoke-DatabaseBuild #create athe build artifcat and export it to file $buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId "SCAPOC" -PackageVersion 1.0.0 $buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\DatabaseBuild\" -Force / comments
# And here is the code that exported the build artifact$ErrorActionPreference = "stop"# Input path to SCA project file$pathToProjectFile = "C:\Users\peter\Documents\IncommSVN_PPD\SCAPOC\SCAPOC\SCAP...