- Ci teamcity how to#
- Ci teamcity install#
- Ci teamcity update#
Then on the Octopus Deploy side, I created 3 separate IIS deploy steps and just followed the typical steps.
In this context, I installed Octopack to the 3 projects in green squares and checked-in the changes. I managed to resolve this by installing the Nuget package Octopack on the projects that I wanted to be deployed as either separate websites or website applications. You may have to play around a bit, but essentially the above is taken from this article so treat that as your bible. /p:OctoPackPublishApiKey=API-ABCDEFGMYAPIKEY.
Publish your packages with the following msbuild arguments:. Ci teamcity update#
Update TeamCity to add /p:RunOctoPack=true to the msbuild command line. Customize the template for each of your projects. This release contains the following changes. nuspec files paste in the following template: csproj, thus if it is you want to create an empty text file called. 
csproj, give it the same base filename as the. Create three empty text files next to the.
Ci teamcity install#
Install OctoPack and read the entire article. nuspec file for each of the IIS websites you want to package: So you need to create packages for each of the three sites so that you can deploy each one individually. Once TC can do that I will need to set-up OD to deploy each of those packages to their required locations (which should hopefully be pretty simple).Īny information/assistance with this is greatly appreciated as I do not have a Dev-Ops background and this is the first time I've had to set-up this kind of a project with TeamCity. The goal is that TC should spit out 3 packages, one for the root website, one for the Signal-R project and one for the API which holds several projects but all projects are entirely in a single solution and this isn't something that I can get around for the time being. So essentially The root website is a client, it communicates can only see API and hubs and any communication to the repository project would go through the API project first, it's supposed to be using a service-orientated architecture. NET project using MVC that communicates, hubs is a Signal-R project and API has the repository project and services project under it. I have manually deployed the solution in IIS, below is how it needs to deploy in IIS: Green boxed will be the separate packages, BLL, Services and Repository because of project dependency get rolled up into the API project.): 
Visual Studio solution set-up (Blue shows the projects that make up the entire application we want to deploy.
Ci teamcity how to#
I currently don't know how to do this.Īnd I have this in my General Settings Publish Artifact settings: I was informed that I should instead have TC take the solution and create multiple packages from it for OP to pick-up. zip on the Dev server, but I've been having issues trying to deploy the solution to IIS with OP. I originally set-up TC to pull the latest from SVC, build the solution and deploy it as a. NET solution that I'm trying to set-up with TeamCity (TC) for CI and Octopus Deploy (OD) for CD.
0 kommentar(er)
