Dot Net Core Application deployment using Octopus


Manage Infrastructure for Deployment using Octopus

After completing my last Article I am sharing my knowledge on further setup of infrastructure and environment for deployment a dot net core application.




You can manage your infrastructure by navigating to the Infrastructure tab in the Octopus Web Portal. From there you can access the following options:



  • ·         Overview
  • ·         Environments
  • ·         Deployment targets
  • ·         Workers
  • ·         Worker pools
  • ·         Machine policies
  • ·         Proxies
  • ·         Accounts

s    Click on create your first environment.



















Set the environment name as I am creating a development environment so I put development as name for the environment.























Add deployment target and select your targeted option. Here I am selecting windows for my case.
























Once you selected Listening Tentacle option then you get the next screen to download the Tentacle.





















Now install the downloaded Tentacle and set few settings in below window.










Set the storage for Tentacle logs and application.































Set the port no for listening tentacle. Also set the octopus thumbprint which you get from creating Tentacle window.






Now install the tentacle.






























Time to add worker on octopus server.





After adding worker you can upload your package.




Here I am creating Dot net core packages to deploy via Octopus. First I created application with help of my last article

Once you completed the package creation task then upload that package from Octopus browser.





Once package is created then you can check it from Package section available in Octopus browser.




In next step I will give detail information on deployment process for uploaded packages. To continue further on deployment you need to create a project on octopus.




Here you will create a new project and give a specific name to it.




After adding project you need to define deployment process.





Time to define life cycle for deployment process. Here I am getting default lifecycle for the deployment of newly created project.





Add a new script for created project and give specific name to that script for further usage. This script will be a window power shell script which is having .PS1 extension.




Add new variable with specific name as displayed in below screen shot.





Now you should choose a step template to set target deployment.





Enable Tenant and connect to project.






After following above steps you can prepare for the release of your project deployment. To create a new build just got to Dashboard and click on create release.





Here you can define version and other related information including package and release notes.
After making changes you just click on save button and initiate octopus for deployment.




Once deployment process is completed then you will get the deployed stuff on earlier defined location. For me it’s in location

F:\RSI\SharjeelsWork\Tentacle\Applications\Development\SharjeelsWork-OctoWeb






After successful deployment you will get the Task progress detail.




With above all described steps you can configure a fresh deployment of your dot net core application. I will try to explain more on Octopus in my next article.



Happy Learning!!! 


























Comments

Post a Comment

Popular posts from this blog

Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0

ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote'

Dot Net Core Application Packaging using Octo