Team City Continuous Integration Configuration

LymeStack can use TeamCity as a Continuous Integration / Continuos (CI/CD) platform. If you don't have Team City installed on your DevOps server, see the DevOps Server Setup Guide. For our documentation we will use the hypothetical project name "MyCompany" to illustrate our examples.

Create a New Project in Team City

The first thing you'll need to do is setup a new project in TeamCity. To do this, log onto your DevOps Server on your remote desktop and navigate to the TeamCity dashboard.

Create a New Project in TeamCity

TODO: Fill this in.

Specify VCS (Git Source Control) configuration.

Define the Build Configuration

Below are the steps used by TeamCity to build the application and deploy to the UAT instance being hosted on IIS on the same machine as the TeamCity build agent. For default beginning use cases, the TeamCity Server, TeamCity Build Agent and UAT IIS Web Server all run on the same server.

Step 1 - NUGET Package Installer

• Solution: MyCompanyApi/MyCompanyApi.sln
• Execute: If all previous steps finished

Step 2 - Build API

• Step Type: .NET
• Working Directory: MyCompanyApi
• Command: publish
• Solution File: MyCompanyApi.sln

Step 3 - Create buildnumber.txt File

• Step Type: Command Line
• Working Directory: MyCompanyApi
• Custom Script:

:: del .\MyCompanyApi\bin\Release\net8.0\win-x64\publish\buildnumber.txt
@echo off
@echo %build.number%> .\MyCompanyApi\bin\Release\net8.0\win-x64\publish\buildnumber.txt

Step 4 - Run Yarn Command

• Step Type: Command Line
• Working Directory: lyme-stack-angular-app
• Custom Script: yarn

Step 5 - Build Angular App

• Step Type: Command Line
• Working Directory: lyme-stack-angular-app
• Custom Script: npm run-script build-debug or npm run-script build-prod

Step 6 - Update Base HREF in index.html File

• Step Type: Powershell
• Working Directory: lyme-stack-angular-app
• Custom Script: (Get-Content .\dist-prod\index.html).replace('<base href="/">', '<base href="/app/"/>') | Set-Content .\dist-prod\index.html

Step 7 - Create NuGet Packages

• Step Type: NuGet Pack
• Specification Files:

my-company-angular-app\dist-prod\MyCompanyAngularApp.nuspec
MyCompanyApi\MyCompanyApi\bin\Release\net8.0\publish\MyCompanyApi.nuspec
MyCompanyApi\MyCompany.DbUp\bin\Release\net8.0\publish\MyCompany.DbUp.nuspec

• Version: %build.number%
• Output directory: nuget-pack-output
• Properties: Configuration=Release

Step 9 - Configure Change Log Data Generation

• Step Type: Powershell
• Working Directory: LymeStackApi/LymeStackApi.Console/bin/Release/net8.0/publish
• Powershell File: CreateChangeLog.ps1

NOTE: You need to change the _baseUrl and _tempCityProjectId in the ChangeLogDataGatherer.cs file. This is not ideal and will be fixed in a future release.

Step 8 - Push Packages to Octopus

Prerequisite: You'll need to configure the deployment process in Octopus prior to completing this step

• Step Type: OctopusDeploy: Push Packages
• Octopus URL: http://localhost:8081
• API Key: API-XXXXXXXXXXXXXXXXXXXXXXXX
• Package paths: nuget-pack-output/*.%build.number%.nupkg

Step 9 - Create Octpus Release to UAT

• Step Type: OctopusDeploy: Create Release
• Octopus URL: http://localhost:8081
• API Key: API-XXXXXXXXXXXXXXXXXXXXXXXX
• Project: MyCompany
• Channel: Default
• Environment(s): UAT
• Additional Command Line Arguments: -Version %build.number% --space Default --gitRef master

Exclude checkins to the .octopus directory from triggering new builds

1. Go to the MyCompany project page in TeamCity.
2. Click "Version Control Settings"
3. Click the "Edit Checkout Rules" option net to the listed VCS Root.
4. Enter the value -:.octopus
5. Click "Save"