Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix namespaces of imports in OctoTools example #468

Merged
merged 1 commit into from
Jun 15, 2014
Merged

Fix namespaces of imports in OctoTools example #468

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions help/octopusdeploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Octopus Deploy relies on the concept of a **release**, which should be an immuta

So once you have created a project you are able to create a push a release into Octopus Deploy. This can be done through the Octopus UI, command line tool, or in our case - from a FAKE script.

open OctoTools
open Fake.OctoTools

Target "Release" (fun _ ->
let release = { releaseOptions with Project = "Order Processor" }
Expand All @@ -52,7 +52,7 @@ You can automatically deploy a release when you create it, but using the optiona

This is often a good idea when you want your FAKE build script to continue on to a second set of perhaps slower, unit tests that exercise behaviours in a more complete and perhaps integrated environment.

open OctoTools
open Fake.OctoTools

Target "ReleaseAndDeploy" (fun _ ->
let release = { releaseOptions with Project = "Order Processor" }
Expand All @@ -73,7 +73,7 @@ In this instance we've used the default `deployOptions` and modified the environ

Finally when you are absolutely happy that your release is good to go the next stage (be that some manual or exploratory testing, or perhaps a staging environment). We can use a `DeployRelease` command to promote an existing release to the next environment:

open OctoTools
open Fake.OctoTools

Target "PromoteRelease" (fun _ ->
let promote = { deployOptions with
Expand Down