Skip to content

Commit ad8871f

Browse files
MrHinshMrHinsh
committed
Merged PR 169: \Updated all names to Azure DevOps
\Updated all names to Azure DevOps
1 parent 37c3e38 commit ad8871f

File tree

11 files changed

+53
-40
lines changed

11 files changed

+53
-40
lines changed

‎README.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
1-
# VSTS Process Template Manager [![Visual Studio Marketplace](https://vsmarketplacebadge.apphb.com/version-short/nkdagility.processtemplate.svg)](https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate)
1+
# Azure DevOps Process Tools [![Visual Studio Marketplace](https://vsmarketplacebadge.apphb.com/version-short/nkdagility.processtemplate.svg)](https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate)
22

3-
This task automates the Process of managing your Process changes from source control to VSTS so that you can keep all your projects in sync.
3+
This task automates the Process of managing your Process changes from source control to Azure DevOps so that you can keep all your projects in sync.
44

5-
One of the largest issues for Enterprise is everyone using a different process template for their projects. When you move your Collection to VSTS with your custom Process Template you get a "Phase 1 enabled account". This account does not let you edit the Process Template in the UI and instead lets you download and upload the process template.
5+
One of the largest issues for Enterprise is everyone using a different process template for their projects. When you move your Collection to Azure DevOps with your custom Process Template you get a "Phase 1 enabled account". This account does not let you edit the Process Template in the UI and instead lets you download and upload the process template.
66

7-
This Build Task lets you upload a local template into VSTS.
7+
These build tasks allow you to manage both the XML and Inherited processes in Azure DevOps Services. You can use this task to create a controlled exposure CI/CD Pipeline that deploys and manages your process between Organisations.
88

99

1010
## What can you do with this tool?
1111

12-
- Upload XML Based Process Template
13-
- Migrate Inherited Process(s) between Organisations (uses [https://github.com/Microsoft/process-migrator](https://github.com/Microsoft/process-migrator))
12+
- **Azure DevOps Services Process (XML)** Task - Upload XML Based Process from an export
13+
- **Azure DevOps Services Process (Inherited)** Task - Migrate Inherited Process(s) between Organisations (uses [https://github.com/Microsoft/process-migrator](https://github.com/Microsoft/process-migrator))
1414

15-
![Screenshot of Process Template Uploader](/images/screenshot-01.png)
15+
![Screenshot of Process Uploader](/images/screenshot-01.png)
1616

17-
Full documentation is available on [https://nkdagility.visualstudio.com/vsts-processtemplate-task/](https://nkdagility.visualstudio.com/vsts-processtemplate-task/)
17+
Full documentation is available on [https://dev.azure.com/nkdagility/vsts-processtemplate-task/](https://dev.azure.com/nkdagility/vsts-processtemplate-task/)
1818

1919
## Getting the Tools
2020

‎docs/index.md‎

Lines changed: 19 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,33 @@
1-
# VSTS Process Template Manager
1+
# Azure DevOps Process Tools [![Visual Studio Marketplace](https://vsmarketplacebadge.apphb.com/version-short/nkdagility.processtemplate.svg)](https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate)
22

3-
Get the [VSTS Process Template Management](https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate) extensions for VSTS from the Marketplace.
3+
This task automates the Process of managing your Process changes from source control to Azure DevOps so that you can keep all your projects in sync.
44

5-
This task automates the Process of uploading your Process Template changes from source control to VSTS so that you can keep all your projects in sync.
5+
One of the largest issues for Enterprise is everyone using a different process template for their projects. When you move your Collection to Azure DevOps with your custom Process Template you get a "Phase 1 enabled account". This account does not let you edit the Process Template in the UI and instead lets you download and upload the process template.
66

7-
One of the largest issues for Enterprise is everyone using a different process template for their projects. When you move your Collection to VSTS with your custom Process Template you get a "Phase 1 enabled account". This account does not let you edit the Process Template in the UI and instead lets you download and upload the process template.
7+
These build tasks allow you to manage both the XML and Inherited processes in Azure DevOps Services. You can use this task to create a controlled exposure CI/CD Pipeline that deploys and manages your process between Organisations.
8+
9+
10+
## What can you do with this tool?
11+
12+
- **Azure DevOps Services Process (XML)** Task - Upload XML Based Process from an export
13+
- **Azure DevOps Services Process (Inherited)** Task - Migrate Inherited Process(s) between Organisations (uses [https://github.com/Microsoft/process-migrator](https://github.com/Microsoft/process-migrator))
14+
15+
![Screenshot of Process Uploader](/images/screenshot-01.png)
16+
17+
Full documentation is available on [https://dev.azure.com/nkdagility/vsts-processtemplate-task/](https://dev.azure.com/nkdagility/vsts-processtemplate-task/)
18+
19+
## Getting the Tools
20+
21+
You can [install from the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=nkdagility.processtemplate)
822

9-
This Build Task lets you upload a local template into VSTS.
1023

1124
## Puting your Template under source control
1225

1326
After you have had your collection imported to VSTS by Microsoft you will be able to download your process template from the administration page.
1427

1528
![List all Process Templates](./assets/vsts-process-template-management-admin.png)
1629

17-
Go to the home page of your VSTS account and head over to "MyAccountName | Account Settings | Process", where you will see a list of the available process templates.
30+
Go to the home page of your Azure DevOps Service Organisation and head over to "MyAccountName | Account Settings | Process", where you will see a list of the available process templates.
1831

1932
![Export Process Templates](./assets/vsts-process-template-management-export.png)
2033

‎inheritedprocessmigration/vCurrent/task.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
{
22
"id": "C6E8CD46-7141-41D1-B21E-9932E08FA67F",
33
"name": "ineritedprocessmigration",
4-
"friendlyName": "VSTS Inherited Process Migration",
5-
"description": "Supports migration/import/export of inherited processes from VSTS Organisations",
4+
"friendlyName": "Azure DevOps Services Process (Inherited)",
5+
"description": "Supports migration/import/export of inherited processes from Azure DevOps Service Organisations",
66
"helpMarkDown": "v1.#{GitVersion.Minor}#.#{GitVersion.Patch}#.#{GitVersion.COMMITSSINCEVERSIONSOURCE}# [More Information](https://github.com/nkdAgility/vsts-process-template-task#readme)",
77
"category": "Deploy",
88
"visibility": [
@@ -141,7 +141,7 @@
141141
"groupName": "options"
142142
}
143143
],
144-
"instanceNameFormat": "VSTS process $(command)",
144+
"instanceNameFormat": "Azure DevOps Services Process $(command)",
145145
"execution": {
146146
"PowerShell3": {
147147
"target": "$(currentDirectory)\\processmigratestart.ps1",

‎processtemplatetask/v1/task.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"id": "63823D31-810C-4957-9BC1-859757ACE94D",
33
"name": "processtemplate",
4-
"friendlyName": "VSTS XML Process Import",
4+
"friendlyName": "Azure DevOps Services Process (XML)",
55
"description": "Deploys an XML Process to VSTS",
66
"helpMarkDown": "v1.#{GitVersion.Minor}#.#{GitVersion.Patch}#.#{GitVersion.COMMITSSINCEVERSIONSOURCE}#2 [More Information](https://github.com/nkdAgility/vsts-process-template-task#readme)",
77
"category": "Deploy",
@@ -27,7 +27,7 @@
2727
{
2828
"name": "account",
2929
"type": "string",
30-
"label": "VSTS Account URL",
30+
"label": "Azure DevOps Service Organisation URL",
3131
"defaultValue": "",
3232
"required": true,
3333
"helpMarkDown": "The URL of the VSTS instance to deploy the Template too. e.g. https://myaccount.visualstudio.com"

‎processtemplatetask/v2/importProcess.ps1‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ $accountURL = [string]$processServiceEndpoint.Url
1818
get-childitem -path env:INPUT_*
1919
get-childitem -path env:ENDPOINT_*
2020

21-
Write-VstsTaskVerbose "VSTS Account: $accountURL"
21+
Write-VstsTaskVerbose "Azure DevOps Service Organisation: $accountURL"
2222
Write-VstsTaskVerbose "Process File: $processFile"
2323
Write-VstsTaskVerbose "Acces Token: $accesstoken"
2424
Write-VstsTaskVerbose "Process GUID: $overrideProcessGuid"

‎processtemplatetask/v2/task.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
{
22
"id": "63823D31-810C-4957-9BC1-859757ACE94D",
33
"name": "processtemplatetask",
4-
"friendlyName": "VSTS XML Process Import",
5-
"description": "Imports an XML Process to VSTS.",
4+
"friendlyName": "Azure DevOps Services Process (XML)",
5+
"description": "Imports an XML Process to Azure DevOps Service.",
66
"helpMarkDown": "v2.#{GitVersion.Minor}#.#{GitVersion.Patch}#.#{GitVersion.COMMITSSINCEVERSIONSOURCE}# [More Information](https://github.com/nkdAgility/vsts-process-template-task#readme)",
77
"category": "Deploy",
88
"visibility": [
@@ -33,7 +33,7 @@
3333
"label": "VSTS XML Process Endpoint",
3434
"defaultValue": "",
3535
"required": true,
36-
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the VSTS Account that you want to connect to. You will need an endpoint per VSTS Account."
36+
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the Azure DevOps Service Organisation that you want to connect to. You will need an endpoint per Azure DevOps Service Organisation."
3737
},
3838
{
3939
"name": "processFile",

‎processtemplatetask/v3/importProcess.ps1‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ $accountURL = [string]$processServiceEndpoint.Url
2020
get-childitem -path env:INPUT_*
2121
get-childitem -path env:ENDPOINT_*
2222

23-
Write-VstsTaskVerbose "VSTS Account: $accountURL"
23+
Write-VstsTaskVerbose "Azure DevOps Service Organisation: $accountURL"
2424
Write-VstsTaskVerbose "Process File: $processFile"
2525
Write-VstsTaskVerbose "Acces Token: $accesstoken"
2626
Write-VstsTaskVerbose "Process GUID: $overrideProcessGuid"

‎processtemplatetask/v3/task.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
{
22
"id": "63823D31-810C-4957-9BC1-859757ACE94D",
33
"name": "processtemplatetask",
4-
"friendlyName": "VSTS XML Process Import",
5-
"description": "Imports an XML Process to VSTS.",
4+
"friendlyName": "Azure DevOps Services Process (XML)",
5+
"description": "Imports an XML Process to Azure DevOps Service.",
66
"helpMarkDown": "v3.#{GitVersion.Minor}#.#{GitVersion.Patch}#.#{GitVersion.COMMITSSINCEVERSIONSOURCE}# [More Information](https://github.com/nkdAgility/vsts-process-template-task#readme)",
77
"category": "Deploy",
88
"visibility": [
@@ -33,7 +33,7 @@
3333
"label": "VSTS XML Process Endpoint",
3434
"defaultValue": "",
3535
"required": true,
36-
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the VSTS Account that you want to connect to. You will need an endpoint per VSTS Account."
36+
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the Azure DevOps Service Organisation that you want to connect to. You will need an endpoint per Azure DevOps Service Organisation."
3737
},
3838
{
3939
"name": "processFile",

‎processtemplatetask/v4/importProcess.ps1‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ $accountURL = [string]$processServiceEndpoint.Url
2020
get-childitem -path env:INPUT_*
2121
get-childitem -path env:ENDPOINT_*
2222

23-
Write-VstsTaskVerbose "VSTS Account: $accountURL"
23+
Write-VstsTaskVerbose "Azure DevOps Service Organisation: $accountURL"
2424
Write-VstsTaskVerbose "Process File: $processFile"
2525
Write-VstsTaskVerbose "Acces Token: $accesstoken"
2626
Write-VstsTaskVerbose "Process GUID: $overrideProcessGuid"

‎processtemplatetask/v4/task.json‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
{
22
"id": "63823D31-810C-4957-9BC1-859757ACE94D",
33
"name": "processtemplatetask",
4-
"friendlyName": "VSTS XML Process Import",
5-
"description": "Imports an XML Process to VSTS.",
4+
"friendlyName": "Azure DevOps Services Process (XML)",
5+
"description": "Imports an XML Process to Azure DevOps Services.",
66
"helpMarkDown": "v4.#{GitVersion.Minor}#.#{GitVersion.Patch}#.#{GitVersion.COMMITSSINCEVERSIONSOURCE}# [More Information](https://github.com/nkdAgility/vsts-process-template-task#readme)",
77
"category": "Deploy",
88
"visibility": [
@@ -30,10 +30,10 @@
3030
{
3131
"name": "VstsXmlProcessService",
3232
"type": "connectedService:VstsXmlProcessEndpoint",
33-
"label": "VSTS XML Process Endpoint",
33+
"label": "Azure DevOps XML Process Endpoint",
3434
"defaultValue": "",
3535
"required": true,
36-
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the VSTS Account that you want to connect to. You will need an endpoint per VSTS Account."
36+
"helpMarkDown": "The endpoint should contain both the Token for access as well a the URL of the Azure DevOps Service Organisation that you want to connect to. You will need an endpoint per Organisation."
3737
},
3838
{
3939
"name": "processFile",

0 commit comments

Comments
 (0)