Dot Net Core Application Packaging using Octo


Octo.exe is a command line tool that interacts with the Octopus Deploy REST API and includes a pack command to create packages either as Zip or NuGet packages for deployment with Octopus.

Installation
We recommend installing Octo as a global tool using .NET Core which makes Octo available as a command via the .NET CLI.
If you have the .NET Core 2.1.300 SDK available you can install Octo onto a machine or build agent as a global tool with the following command:
dotnet tool install Octopus.DotNet.Cli –global







Publish your application
There are two ways to publish your dot net core application. One you can do from command line and other from Dote net solution it self.
Command Line
Dot net publish source/sharjeelsWorkCore.Web --output published-app --configuration Release
dotnet publish F:\RSI\SharjeelsWork\RD\Core\sharjeelsWorkCore\sharjeelsWorkCore\sharjeelsWorkCore.csproj --output published-app --configuration Release








Dote Net Solution
Right click on your Dot net core project and select publish.







Once publishing is completed then you can check published item from given location. In my case location was
F:\RSI\SharjeelsWork\RD\Core\sharjeelsWorkCore\sharjeelsWorkCore\bin\Release\netcoreapp2.1\publish







At a minimum Octo pack requires an ID to be provided. Also if you want to provide your own version, you can pass the --version parameter in the call to Octo.
You can also change the output directory and folder which will be packed with the --outFolder and --basePath parameters respectively. I am combining all three point in single command

dotnet octo pack --id="SharjeelsWork-OctoWeb" --version="1.0.6" --format=zip --basePath=" F:\RSI\SharjeelsWork\RD\Core\sharjeelsWorkCore\sharjeelsWorkCore\bin\Release\netcoreapp2.1\publish" --outFolder=" F:\RSI\SharjeelsWork\Octopus\Packages\DotNetCore"









Upgrade Octo version
If you would like to update to a specific version or downgrade to an older version you can do so by first uninstalling the tool and installing it again.

dotnet tool uninstall Octopus.DotNet.Cli --global
dotnet tool install Octopus.DotNet.Cli --global --version <version>

whenever you are creating dot net core packages through command line, take care of location path and version. In next article I will try to describe more on Octopus deployment.



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

Image
I got above error after adding dependency in Maven POM xml file placed under newly created AEM arch type and running command  mvn -PautoInstallPackage clean install . 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 After google and gone through few article I got command ( mvn -PautoInstallPackage -Padobe-public clean install) . Once I run this command this issue with jar compatibility was resolved. Happy Learning!!!
Read more

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'

I was getting below error while working with cache management on CM and CD server. Actually my code was working fine on CM server but I was not able to access or clear cache object on CD server because of wrong event selection.  PID[18108] Error       ManagedPoolThread #3 16:24:16 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' event.Source: Sitecore.Kernelat Sitecore.Events.Event.EventSubscribers.RaiseEvent(String eventName, Object[] parameters, EventResult result)at Sitecore.Events.Event.RaiseEvent(String eventName, Object[] parameters)at Sitecore.Eventing.Subscription`1.Invoke(Object instance, EventContext context)at Sitecore.Eventing.EventProvider.RaiseEvent(Object event, Type eventType, EventContext context) Above error comes due to wrong event args access in CD server. T...
Read more

Error : Sorry, there was an error : unauthorized_client in Sitecore 9.1 login

Image
After adding a new binding from IIS on my sitecore 9.1 instance I was getting unauthorized client error while login with newly added binding URL. To fix this issue I added AllowedCorsOriginsGroup in xml file placed at File Name :  Sitecore.IdentityServer.Host.xml Location : C:\inetpub\wwwroot\9Dot1.identityserver\Config\production After adding field tag AllowedCorsOriginsGroup in  Sitecore.IdentityServer.Host.xml file I was able to login properly with newly added URL. Also you can fix this issue by placing a pipe operator beside of old AllowedCorsOriginsGroup as below. <AllowedCorsOriginsGroup1>http://9Dot1.sc | http://jss.9Dot1.sc</AllowedCorsOriginsGroup1 Happy Learning!!!
Read more