150 likes | 469 Views
Getting started with Octopus Deployment. Joel Hammond-Turner E: joel@hammond-turner.org.uk T: @ Rammesses. Repeatable, automated deployment To target server(s) Across server farms. To the cloud Azure / Amazon AWS. Why Deploy?. Release control Deploy the binaries, not a new build.
E N D
Getting started with Octopus Deployment Joel Hammond-Turner E: joel@hammond-turner.org.uk T: @Rammesses
Repeatable, automated deployment • To target server(s) • Across server farms. • To the cloud • Azure / Amazon AWS Why Deploy?
Release control • Deploy the binaries, not a new build. • Traceability / versioning • Test / approval cycles • Configuration Why Deploy?
CI The Deployment Cycle (That one extra slide)
Release Control System • Deploy the binaries, not a new build. • Traceability / versioning • Test / approval cycles • Configuration Transforms ✓ ✓ ✓ ✓ Why Octopus?
NuGet / Powershell based • Integrates with CI (TFS / TeamCityetc) • Works with Windows Azure • FREE (for one project) • $349 – for 3 projects • $799 – for unlimited projects What is Octopus?
Configuration Transforms Test Server Your Software UAT Servers NuGet Server Octopus Server Live Servers How does it work?
Octopack • Packages website within a NuGet package. • /p:RunOctoPack = true • Enables upload-on-build • /p:OctoPackPublishPackageToFileShare = … • /p:OctoPackPublishPackageToHttp = … • /p OctoPackPublishApiKey = … Packaging Websites
Azure Deployment Step • /t:Publish • Creates a cspkg file Deploying to Azure
Azure Deployment Package • No tooling currently… • but… NuGet.PackageNPublishworks!* * With tweaks. Deploying to Azure
Deploying to Azure Demo
Octopus Deploy • Provides repeatable, automated deployment of websites (or other apps). • NuGet / Powershell Based • Deploys to Azure • “Does what is says on the tin” Summary
Getting started with Octopus Deployment Joel Hammond-Turner E: joel@hammond-turner.org.uk T: @Rammesses