User profile for PeterDaniels

I think I found the answer here: https://documentation.red-gate.com/sca3/getting-started/requirements/powershell-component-requirements Apparently linux Jenkins nodes won't fly. / comments

I think I found the answer here: https://documentation.red-gate.com/sca3/getting-started/requirements/powershell-component-requirements Apparently linux Jenkins nodes won't fly.

0 votes

Thanks @Dan B. It felt awkward to me because I had set up the connection to the dev DB multiple times but when I clicked on the "finish setting up the project", it did not show that connection. It asked for me to connect to a dev DB. As far as I was concerned, I was done setting up the project. It's a minor annoyance, but still felt like a bug. So, yes, please send this on to the devs. Thank you, -Peter / comments

Thanks @Dan B. It felt awkward to me because I had set up the connection to the dev DB multiple times but when I clicked on the "finish setting up the project", it did not show that connection. It ...

0 votes

oops / comments

oops

0 votes

@Monday - I love how your'e thinking here. I was considering adding that functionality to make it more robust, but decided on a quick dev first. / comments

@Monday - I love how your'e thinking here. I was considering adding that functionality to make it more robust, but decided on a quick dev first.

0 votes

I did, @Monday. Here's the function: $VersionInfo = Get-LatestVersionAndMigrationNumber -ProjectFilePath $ProjectFilePath $PackageVersion = $VersionInfo.Version + '-migration' + $VersionInfo.MigrationNumber $ReleaseVersion = $PackageVersion </code># Get latest version and migration from project file path # This is cool. Version like 1.1.0 and Migration number like 5 - to build ReleaseVersion and/or PackageVersion function Get-LatestVersionAndMigrationNumber { [CmdletBinding()] param ( [parameter(Mandatory=$true)] [string] $ProjectFilePath ) process { # First, strip the project file name and find the Migrations folder $ProjectRootFolder = Split-Path -Path $ProjectFilePath $MigrationsFolder = Join-Path -Path $ProjectRootFolder -ChildPath "Migrations" if (-not (Test-Path -Path $MigrationsFolder)) { Write-Error -Message "Invalid path: $MigrationsFolder" exit } # Get the latest migration folder sem ver [string]$Latest = Get-ChildItem -Path $MigrationsFolder -Directory | ForEach-Object {[Version]($_.Name -split "-")[0]} | Sort-Object -Descending | Select -First 1 # Get the base folder back now that I found the latest version: $LatestFolder = Get-ChildItem -Path $MigrationsFolder -Directory | Where-Object {$_.Name -like "$Latest*"} # Now get the migrations in that folder $LatestMigrationsFolder = Join-Path -Path $MigrationsFolder -ChildPath $LatestFolder $LatestMigration = (Get-ChildItem -Path $LatestMigrationsFolder -File).Name | Sort-Object -Descending | select -First 1 [int]$LatestMigrationSequenceNumber = ($LatestMigration -split "_")[0] # Return a custom object with the latest sem version and migration sequence num #$Latest + "-migration" + $LatestMigrationSequenceNumber $obj = New-Object -TypeName PSCustomObject -Property @{Version = $Latest;MigrationNumber = $LatestMigrationSequenceNumber} $obj } } </pre><div>I then use it:<br><pre class="CodeBlock"><code>To create a version that looks like (for example) 1.1.0-migration14 / comments

I did, @Monday. Here's the function:$VersionInfo = Get-LatestVersionAndMigrationNumber -ProjectFilePath $ProjectFilePath $PackageVersion = $VersionInfo.Version + '-migration' + $VersionInfo.Migrati...

0 votes

One more comment for RG folks: I would still expect the PackageVersion SQLCMD var to be populated in the PackageScript.sql after I call Export-DatabaseBuildArtifact, since we are required to call that cmdlet with a PackageVersion parameter. / comments

One more comment for RG folks: I would still expect the PackageVersion SQLCMD var to be populated in the PackageScript.sql after I call Export-DatabaseBuildArtifact, since we are required to call t...

0 votes

Oddly,I am not able to select @way0utwest 's response as the answer to my question... / comments

Oddly,I am not able to select @way0utwest 's response as the answer to my question...

0 votes

@Eddie D and @Monday , thanks for the replies. Eddie, I am aware of the docs you suggested. That still requires the ops DBA to use powershell to deploy, so it's not an option until I socialize that possibility. Currently, I'm trying to automate as much as possible before delivering them a sql file. I would like to see an option to set various SQLCMD vars in the packagescript.sql when I call invoke-databaseBuild. / comments

@Eddie D and @Monday , thanks for the replies. Eddie, I am aware of the docs you suggested. That still requires the ops DBA to use powershell to deploy, so it's not an option until I socialize that...

0 votes

I guess it makes sense that package version might not be set since I can actually get the PackageScript.sql without calling Export-DatabaseBuildArtifact. Re: ReleaseVersion, I understand that I could set it in the project on the SQLCMD vars tab, but I want it to be dynamically set via powershell. Since Invoke-DatabaseBuild doesn't have a SqlCmdVariables param like New-DatabaseReleaseArtifact does, I don't see a programmatic way to set release version other than processing the file, which I have to do anyway side the SQLCMD setvar section is commented out anyhoo. / comments

I guess it makes sense that package version might not be set since I can actually get the PackageScript.sql without calling Export-DatabaseBuildArtifact.Re: ReleaseVersion, I understand that I coul...

0 votes

Gotcha. Thank you, @way0utwest. / comments

Gotcha. Thank you, @way0utwest.

0 votes

How can we help you today?

PeterDaniels

Comments