Deployment Groups

AC Maintenance CI

ALWAYS REUSE AC_DEPLOYMENT GROUPS (Baaki-2024 project) FROM DIFFERENT SERVERS WHENEVER POSSIBLE. If reuse is not possible, follow the below steps
Go to Deployment groups. Click Add a deployment group

Give appropriate name to the deployment group, copy the script and run it in theTARGET SERVER. (This step should not be skipped. If the below script is directly run in the target server without creaing the deployment group in the project pipe line, the below script will throw error mentioning "deployment group not found." Make sure the deployment group name created in the project pipeline deployment group matches the deployment group name in the below script, before running it in the target server)

Please use the below script. Rename the deployment group name, agent location, agent name, project org name and server name as appropriate

$ErrorActionPreference="Stop";If(-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent() ).IsInRole( [Security.Principal.WindowsBuiltInRole] "Administrator")){ throw "Run command in an administrator PowerShell prompt"};If($PSVersionTable.PSVersion -lt (New-Object System.Version("3.0"))){ throw "The minimum version of Windows PowerShell that is required by the script (3.0) does not match the currently running version of Windows PowerShell." };If(-NOT (Test-Path $env:SystemDrive\'ac_deploymentgroups'\'azagent01')){mkdir $env:SystemDrive\'ac_deploymentgroups'\'azagent01'}; cd $env:SystemDrive\'ac_deploymentgroups'\'azagent01'; for($i=1; $i -lt 100; $i++){$destFolder="A"+$i.ToString();if(-NOT (Test-Path ($destFolder))){mkdir $destFolder;cd $destFolder;break;}}; $agentZip="$PWD\agent.zip";$DefaultProxy=[System.Net.WebRequest]::DefaultWebProxy;$securityProtocol=@();$securityProtocol+=[Net.ServicePointManager]::SecurityProtocol;$securityProtocol+=[Net.SecurityProtocolType]::Tls12;[Net.ServicePointManager]::SecurityProtocol=$securityProtocol;$WebClient=New-Object Net.WebClient; $Uri='https://vstsagentpackage.azureedge.net/agent/3.225.2/vsts-agent-win-x64-3.225.2.zip';if($DefaultProxy -and (-not $DefaultProxy.IsBypassed($Uri))){$WebClient.Proxy= New-Object Net.WebProxy($DefaultProxy.GetProxy($Uri).OriginalString, $True);}; $WebClient.DownloadFile($Uri, $agentZip);Add-Type -AssemblyName System.IO.Compression.FileSystem;[System.IO.Compression.ZipFile]::ExtractToDirectory( $agentZip, "$PWD");.\config.cmd --deploymentgroup --deploymentgroupname "prod-ex-prxy-01 deployment group" --agent "prod-ex-prxy-01_azagent01" --runasservice --work '_work' --url 'https://pm.aspireclan.com/' --collectionname 'FinPlan-Org' --projectname 'Baaki-2024'; Remove-Item $agentZip;

Execute the above step in the respective servers below: (if the deployment groups are already existing in the server through other project(s), use those as a shared deployment group on in this project)

Deployment Groups
Category	Development	QA	Production	Comments
App	dev-app-01	qa-app-01	prod-app-01	One agent each for all services (gw, auth, data, file, script, scheduler [windows service], etc.) per server
Web	dev-web-01	qa-web-01	prod-web-01	Only one agent for web application per server
Load Balancer (LB)	dev-lb-01	qa-lb-01	prod-lb-01	One agent for the API gateway and another one for the Web Application per server
Proxy	dev-proxy-01	qa-proxy-01	prod-in-prxy-01 prod-ex-prxy-01	One agent for the API gateway and another one for the Web Application per server
File	dev-file-01	qa-file-01	prod-file-01	Only one agent for the file service per server
Swagger	NA	NA	prod-docs-01	One agent each for all services (gw, auth, data, file, script, etc.) per server. Currently only PROD server is being used