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. I’ve chosen MS SQL Server as that’s what everything else is running on, which required a JDBC driver. Once that installed, I had to hit refresh
- For the server details, I used CABAL as the Database host, SQLEXPRESS as the Instance Name (the one I decided would be production), and left the name blank and Windows Authentication. I got “The server sqlexpress is not configured to listen with TCP/IP.: com.microsoft.sqlserver.jdbc.SQLServerException: The server sqlexpress is not configured to listen with TCP/IP.” 5a. I’ve gone to the SQL Server Configuration Manager via Control Panel -> Administrative tools -> Open Computer Management ->Services and Application -> SQl server configuration manager, then I went to SQL Server Network Configuration -> Protocols for SQLEXPRESS -> right click and enable TCP/IP. Then I used the Windows Services manager to stop and start the service.
- Now TeamCity threw and error about being unable to create a table in the master database. I probably should have specified a different one. I stopped and restarted the TeamCity Service and Build Agent, which meant the setup process started again when I went to http://localhost:8111. This time I named the database TeamCity but it failed since that DB does not exist.
- I created the DB, but TeamCity is not getting to log in. I need to figure this out - what sort of login and account do I need?
I suspect this is going to be frustrating. Maybe not worth it, since it’s very related to what I currently do at Youi. Maybe I would be better off focussing on widening my experience with cloud-based tools in the Azure platform?