![]() ![]() I’ve also created a TeamCity meta-runner which you can use as a build. After that, you can publish the generated file to the Octopus server with octo.exe or TeamCity plugin. TLDR - If you want to deploy projects in a solution as separate websites, install the Octopus Deploy plugin to TeamCity and follow the basic tutorials, add the Octopack NuGet package to the projects you want as separate websites or web applications, set-up the Octopack step to push to Octopus Deploy over the API and use IIS steps in Octopus Deploy and you should be golden. The extended script grabs all the changes from a TeamCity build and tries to retrieve the tasks’ information from Jira and generates a markdown file with release notes. Octopus deploy now receives a NuGet package from TeamCity using the Octopus deploy plugin, Octopack build step, from there Octopus deploy has 3 IIS deploy steps, one for the main website and 2 for the website applications, each was given a custom directory path but after I had installed the Octopack NuGet packages into the appropriate projects in the solution through Visual Studio it was smooth sailing just using the general user-guide and tutorial slater - Thank-you for letting me know about Octopack and nuspec, these were some of the key missing pieces that I needed. 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. The solution is currently deployed on ISS like this:Īny assistance provided or links to resources is deeply appreciated. Information about the solution and environment: ![]() I've looked through the documentation and spent a lot of time Googling but I haven't found an example of someone doing this but I want to use Octopush Deploy because of the reporting and flexibility it provides (since I will need to set up pipelines to other environments in the future). Is this something that I can accomplish with Octopus Deploy, and if so how? The package itself is a solution that contains several projects, and each project needs to be deployed to different folders on IIS. I'm using TeamCity which I have configured using the Octopus Deploy plugin to create a Nuget package to the appropriate dev server (alternatively, I can have TeamCity spit out a. I'm tasked with setting up CI/CD for my company. The problem is Octopus Deploy will prevent you from deploying these revisions because it sees the same NuGet package version and thinks nothing has changed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |