Change Automation Project

Alright, now that Octopus kind of works, I want to get signed up for TeamCity and get that installed on my local machine. I’ve Googled “TeamCity” and ended up at https://www.jetbrains.com/teamcity/download/#section=on-premises where I downloaded TeamCity for on-prem I changed the installation directory to my secondary hard drive, but otherwise left all the settings on their default, including the port (8111) and the build agent properties (which popped up after the install) Run TeamCity Agent under the SYSYEM account and Start both services As it started it asked for the database type to store the build history....

Open the Octopus Manager and make sure the service has started, then naviate to the web portal (mine is at http://localhost/app#/) On the portal, Create your first environment and Add Environment, naming it Test, then Add Deployment Target (reading https://octopus.com/docs/infrastructure/deployment-targets) Select Windows for the type of target, then Listening Tentacle. Download the Tentacle (I chose 64 bit) Run the tentacle installer, installing in default location, and start the Tentacle Manager Select Get Started, then Listening Tentacle....

So now that I have my instances installed I can work on actually getting Octopus installed and connected correctly. Here are the steps I followed: Sign up for Octopus: https://octopus.com/start I selected the Server version, used a dummy company name, and created my account Downloaded the file and installed it into the default location I selected “Get Started” and pasted in the licence key I was emailed I chose my secondary hard drive for the deployment files, D:\Octopus I chose the option “Use Local System Account” I chose the production “SQLEXPRESS” server, and default “OctopusDeploy-OctopusServer” database Default HTTP listen port 80 sa....

My plan was to create two virtual machines that would mostly lay dormant, and install SQL Server Express on both of them. One of them would be my test environment, and one would be my live environment, with my local machine acting as development. I started googling “virtual machine windows 10” and following the Hyper-V application notes (Microsoft Documentation). First, I needed to create an .iso file: Microsoft Documentation I didn’t need a USB, but I simply ran the tool and selected “Create an ....