functions/Add-DBOBuild.ps1
|
function Add-DBOBuild { <# .SYNOPSIS Creates a new build in existing DBOps package .DESCRIPTION Creates a new build in existing DBOps package from specified set of scripts. .PARAMETER ScriptPath A collection of script files to add to the build. Accepts Get-Item/Get-ChildItem objects and wildcards. Will recursively add all of the subfolders inside folders. See examples if you want only custom files to be added. During deployment, scripts will be following this deployment order: - Item order provided in the ScriptPath parameter - Files inside each child folder (both folders and files in alphabetical order) - Files inside the root folder (in alphabetical order) Aliases: SourcePath .PARAMETER Path Path to the existing DBOpsPackage. Aliases: Name, FileName, Package .PARAMETER Build A string that would be representing a build number of this particular build. Optional - can be genarated automatically. Can only contain characters that will be valid on the filesystem. .PARAMETER Type Adds only files that were not added to the package yet. The following options are available: * New: add new files based on their source path (can be relative) * Modified: adds files only if they have been modified since they had last been added to the package * Unique: adds unique files to the build based on their hash values. Compares hashes accross the whole package * All: add all files regardless of their previous involvement More than one value can be specified at the same time. Default value: All .PARAMETER Absolute All the files in -Path will be added using their absolute paths instead of relative. .PARAMETER Relative Use current location to build relative paths instead of starting from the folder in -Path. .PARAMETER NoRecurse Only process the first level of the target -Path. .PARAMETER Match Runs a regex verification against provided file names using the provided Match string. Example: .*\.sql .PARAMETER Confirm Prompts to confirm certain actions .PARAMETER WhatIf Shows what would happen if the command would execute, but does not actually perform the command .EXAMPLE # Add new build 2.0 to the existing package using files from .\Scripts\2.0 Add-DBOBuild -Path MyPackage.zip -ScriptPath .\Scripts\2.0 -Build 2.0 .EXAMPLE # Add new build 2.1 to the existing package using modified files from .\Scripts\2.0 Get-ChildItem .\Scripts\2.0 | Add-DBOBuild -Path MyPackage.zip -Build 2.1 -Type Unique .EXAMPLE # Add new build 3.0 to the existing package checking if there were any new files in the Scripts folder Add-DBOBuild -Path MyPackage.zip -ScriptPath .\Scripts\* -Build 3.0 -Type New .NOTES See 'Get-Help New-DBOPackage' for additional info about packages. #> [CmdletBinding(SupportsShouldProcess)] [Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSReviewUnusedParameter", "")] param ( [Parameter(Mandatory = $true, Position = 1)] [Alias('FileName', 'Name', 'Package')] [string]$Path, [Parameter(Mandatory = $true, ValueFromPipeline = $true, Position = 2)] [Alias('SourcePath')] [object[]]$ScriptPath, [string]$Build, [ValidateSet('New', 'Modified', 'Unique', 'All')] [string[]]$Type = 'All', [switch]$Absolute, [switch]$Relative, [switch]$NoRecurse, [string[]]$Match ) begin { if (!$Build) { $Build = Get-NewBuildNumber } $scriptCollection = @() } process { Write-PSFMessage -Level Verbose -Message "Processing path items $ScriptPath" $scriptCollection += Get-DbopsFile $ScriptPath } end { Write-PSFMessage -Level Verbose -Message "Loading package information from $Path" if ($package = Get-DBOPackage -Path $Path) { #Prepare the scripts that's going to be added to the build $scriptsToAdd = @() foreach ($childScript in $scriptCollection) { # Include file by default $includeFile = $Type -contains 'All' if ($Type -contains 'New') { #Check if the script path was already added in one of the previous builds if (!$package.PackagePathExists($childScript.PackagePath)) { $includeFile = $true Write-PSFMessage -Level Verbose -Message "File $($childScript.PackagePath) was not found among the package source files, adding to the list." } } if ($Type -contains 'Modified') { #Check if the file was modified in the previous build if ($package.ScriptModified($childScript)) { $includeFile = $true Write-PSFMessage -Level Verbose -Message "Hash of the file $($childScript.FullName) was modified since last deployment, adding to the list." } } if ($Type -contains 'Unique') { #Check if the script hash was already added in one of the previous builds if (!$package.ScriptExists($childScript.FullName)) { $includeFile = $true Write-PSFMessage -Level Verbose -Message "Hash of the file $($childScript.FullName) was not found among the package scripts, adding to the list.." } } if ($includeFile) { $scriptsToAdd += $childScript } else { Write-PSFMessage -Level Verbose -Message "File $($childScript.FullName) was not added to the current build due to -Type restrictions: $($Type -join ',')" } } if ($scriptsToAdd) { #Create new build object $currentBuild = $package.NewBuild($Build) foreach ($buildScript in $scriptsToAdd) { $currentBuild.AddScript($buildScript) Write-PSFMessage -Level Verbose -Message "Adding file '$($buildScript.FullName)' to $currentBuild as $($buildScript.GetPackagePath())" } if ($pscmdlet.ShouldProcess($package, "Writing new build $currentBuild into the original package")) { $currentBuild.Alter() } } else { Write-Warning "No scripts have been selected, the original file is unchanged." } $package } } } |