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.

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

Spelling #317

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions .octopus/deployment_process.ocl
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ step "Queue and verify a test build" {
$tokenBytes = [System.Text.Encoding]::UTF8.GetBytes(":$AccessToken");
$base64Pat = [System.Convert]::ToBase64String($tokenBytes);

$builParameters = ConvertTo-Json @{
$buildParameters = ConvertTo-Json @{
"system.debug" = "true"
"BuildConfiguration" = "debug"
"BuildPlatform" = "x64"
Expand All @@ -104,7 +104,7 @@ step "Queue and verify a test build" {
"id" = $TestProjectDefinitionId
}
"sourceBranch" = "refs/heads/master"
"parameters" = $builParameters
"parameters" = $buildParameters
} -Depth 100

#$postData = '{"definition": {"id": ' + $TestProjectDefinitionId + ',"sourceBranch": "refs/heads/master", "parameters": "{\"system.debug\":\"true\",\"BuildConfiguration\":\"debug\",\"BuildPlatform\":\"x64\"}"}"}'
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ This extension provides a friendly interface to the [Octopus CLI](https://g.octo

## Dev

Microsoft TFS/ADO web extensions are powered by Node.js under the hood. Simply open the repo with your favourite text editor like [Jetbrains WebStorm](https://jetbrains.com/webstorm) or [Visual Studio Code](https://code.visualstudio.com/) and you're good to go.
Microsoft TFS/ADO web extensions are powered by Node.js under the hood. Simply open the repo with your favourite text editor like [JetBrains WebStorm](https://jetbrains.com/webstorm) or [Visual Studio Code](https://code.visualstudio.com/) and you're good to go.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

brand


## Building

Expand Down
2 changes: 1 addition & 1 deletion source/tasks/Deploy/DeployV6/task.json
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@
"label": "Values for prompted variables",
"defaultValue": "",
"required": false,
"helpMarkDown": "Variable values to pass to the the deployment, use syntax `variable: value`"
"helpMarkDown": "Variable values to pass to the deployment, use syntax `variable: value`"
},
{
"name": "UseGuidedFailure",
Expand Down
2 changes: 1 addition & 1 deletion source/tasks/DeployTenant/TenantedDeployV6/task.json
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@
"label": "Values for prompted variables",
"defaultValue": "",
"required": false,
"helpMarkDown": "Variable values to pass to the the deployment, use syntax `variable: value`"
"helpMarkDown": "Variable values to pass to the deployment, use syntax `variable: value`"
},
{
"name": "UseGuidedFailure",
Expand Down
4 changes: 2 additions & 2 deletions source/vsts.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@ Options include:

## Version 6 of Deploy Release step

From version 6, the deploy release step is split into two seperate functions for normal deployments and tenanted deployments
From version 6, the deploy release step is split into two separate functions for normal deployments and tenanted deployments

### <a name="deploy-octopus-release"></a>![Deploy Release Image](img/octopus_deploy-02.png) Deploy Octopus Release (v6 or later)

Expand Down Expand Up @@ -306,7 +306,7 @@ The `Step` input parameter needs to be set to the `name` of the deployment step

| Name | Description |
| :--------------------------------- |:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `completed_successfully` | True if all execution tasks completed succcessfully, false if any execution tasks failed. |
| `completed_successfully` | True if all execution tasks completed successfully, false if any execution tasks failed. |
| `server_task_results` | JSON representation of the tasks and their success. Schema: { "serverTaskId": <task id>, "tenantName": <tenant name>, "environmentName": <environment name>, "successful": <true/false> } |
| `<context>.completed_successfully` | Contextual success flag for each task using the name of the environment or tenant, e.g `production.completed_successfully` or `uat_tenant.completed_successfully`. Spaces in names are replaced with underscores |

Expand Down