CI / CD Process Update: octopus deploy

Octopus: General

1. An instance in IIS that has its own pool and that "looks" in document root. A separate pool is allocated for each module.
2. Core package files in document root.
3. Individual package files in document root.
4. It is advisable to backup the old contents of document root in front of all this. We, of course, are confident in ourselves, but people are divided into two types: those who do not backup, and those who already do. 
5. ( ) ( ). , , .
6. , , .
7. , .
8. () .

Tenants

• env.tenantRoleTag variable - contains TenantRole (tenant tag name in octopus), and its actual value;
• env.modName - The value of the ModName tag in octopus.

Variables

• base paths to document root (for example, C: \ inetpub \);
• base URL (for example, for all modules the common domain is organization.com);
• access to databases (needed to organize backups);
• etc.

Channels

Patterns

$url = "$scheme" + "://" + "$domain"
Write-Host "Requesting '$url'"
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$request = [System.Net.WebRequest]::Create($url)
$request.Timeout = $timeout
$response = $request.GetResponse()
$response.Close()

Octopus: process details

• core;
• individual module projects.

Deployment process core

• all significant parameters are set by variables, this allows you to quickly change their value in one place without digging deep into the process settings;
• the IIS pool name matches the instance name and the service domain name (for convenience);
• in the deploy IIS step, Merge with existing bindings is installed, instead of replacing. Since in addition to the service one, we still have a bunch of client domains at each instance;
• Cleaning up document root (checkmark purge this directory before installation) fails. New files replace old ones as you copy. This is done so that the site does not “crash” during the deployment. The delay in loading the page is much nicer than the death screen.

$days = $OctopusParameters["DaysStoreBackups"]
$limit = (Get-Date).AddDays(-$days)
$pathDb = $OctopusParameters["DbBackupDir"]
$pathFiles = $OctopusParameters["FilesBackupDir"] + '\' + $OctopusParameters["HostName"]

# Delete files older than the $limit.
Get-ChildItem -Path $pathDb -Recurse -Force | Where-Object { !$_.PSIsContainer -and $_.CreationTime -lt $limit } | Remove-Item -Force
# Delete any empty directories left behind after deleting the old files.
Get-ChildItem -Path $pathDb -Recurse -Force | Where-Object { $_.PSIsContainer -and (Get-ChildItem -Path $_.FullName -Recurse -Force | Where-Object { !$_.PSIsContainer }) -eq $null } | Remove-Item -Force -Recurse

# Delete files older than the $limit.
Get-ChildItem -Path $pathFiles -Recurse -Force | Where-Object { !$_.PSIsContainer -and $_.CreationTime -lt $limit } | Remove-Item -Force
# Delete any empty directories left behind after deleting the old files.
Get-ChildItem -Path $pathFiles -Recurse -Force | Where-Object { $_.PSIsContainer -and (Get-ChildItem -Path $_.FullName -Recurse -Force | Where-Object { !$_.PSIsContainer }) -eq $null } | Remove-Item -Force -Recurse

The deployment process of an individual package

• In the deploy step, document root is not cleaned up (the new core package is already there);

$baseDomain = $OctopusParameters["HostName"]
$domains = (Get-WebBinding $baseDomain).bindingInformation | %{ $_.Split(':')[2] } | Sort-Object | Get-Unique
Write-Host "##teamcity[setParameter name='AllInstanceDomains' value='$domains']"
Write-Host "##teamcity[setParameter name='ServiceDomain' value='$baseDomain']"

Write-Host "All domains on instance %ServiceDomain% :"
$domains = "%AllInstanceDomains%"
$domains = $($domains.Split(" ") | ForEach-Object {"http://$_"} | Out-String)
Write-Host $domains
Write-Host "Service domain: http://%ServiceDomain%"

Octopus: results

• code is collected from a specific branch (corresponding to the environment);
• the result of the assembly (artifacts) is given to the octopus and consists of two parts: the kernel and an individual module package. This allows for efficient use of disk space and saves overall update delivery time. 
• Each package has a version consisting of a number and a pre-release tag that defines the channel and the environment in which this release will fall.
• Octopus, by input, creates a release and delivers packets to the appropriate servers, guided by the organization data (tenant tags), channels (pre-release tag) and additional instructions (optional backup of the database), and also makes an elementary check of the module’s performance.