You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/articles/migration-overview.md
+5-4
Original file line number
Diff line number
Diff line change
@@ -81,23 +81,24 @@ A: No, when it comes to service updates, Hosted XML organizations are treated th
81
81
82
82
#### Q: Will my organization be stuck in Hosted XML forever?
83
83
84
-
A: You are using the Hosted XML because the Inheritance process model does not contain all features yet. We are planning to allow you to migrate from the Hosted XML into the Inheritance process model later this year.
84
+
A: You are using the Hosted XML process because the Inheritance process model does not contain all features yet. However, you can now [clone a hosted XML process to an Inheritance process](https://docs.microsoft.com/azure/devops/organizations/settings/work/upgrade-hosted-to-inherited).
85
85
86
86
#### Q: Will migrating from Hosted XML into Inheritance process model be a manual process?
87
87
88
-
A: No, the plan is to provide a simple and automated experience through the web interface.
88
+
A: No, the migration is automated. Simply follow the steps to [clone a hosted XML process to an Inheritance process](https://docs.microsoft.com/azure/devops/organizations/settings/work/upgrade-hosted-to-inherited).
89
+
89
90
90
91
#### Q: What happens in Hosted XML when Microsoft makes a change to a system process?
91
92
92
93
A: This is the same experience with TFS on-premises. If we make a change to a system process, it will not be applied to any of your Hosted XML processes. You won't have to update your processes if you don't want to. But if you do, you will need to make the changes in the XML definition files manually for each process.
93
94
94
95
#### Q: Is there a difference between a team project that was created manually versus one that was created from data import?
95
96
96
-
A. The features available to each team project are the same. The differences occur in how you modify the processes in your organization. When you create an organization, you will use the [Inheritance process model](../organizations/settings/work/manage-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json) to customize the work tracking experience. Team projects migrated via data import, however, will use the [Hosted XML process model](../organizations/settings/work/import-process/import-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json) to customize the work tracking experience.
97
+
A. The features available to each team project are the same. The differences occur in how you modify the processes in your organization. When you create an organization, you will use the [Inheritance process model](../organizations/settings/work/manage-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json) to customize the work tracking experience. Team projects migrated via data import, however, will use the [Hosted XML process model](../organizations/settings/work/import-process/import-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json) to customize the work tracking experience. As described above, these Hosted XML processes can be cloned to an Inheritance process model after import.
97
98
98
99
#### Q: If my organization is using Hosted XML, can I create new projects to use the Inheritance process model?
99
100
100
-
A: Yes. For data import organizations, Azure DevOps Services supports team projects that use Inheritance as well as Hosted XML process models. To learn more about the Inheritance process, see [Manage processes](../organizations/settings/work/manage-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json).
101
+
A: Yes. For data import organizations, Azure DevOps Services supports team projects that use Inheritance as well as Hosted XML process models. To learn more about the Inheritance process, see [Manage processes](../organizations/settings/work/manage-process.md?toc=/azure/devops/reference/toc.json&bc=/azure/devops/reference/breadcrumb/toc.json).
101
102
102
103
#### Q: Where can I find more information on Hosted XML and the Inheritance process model?
This command will retrieve all the log messages, extract the usernames, eliminate any duplicate usernames, sort the usernames, and place them into a "authors-transform.txt" file. You can then edit each line in the file to create a mapping of SVN users to a well-formatted Git user. For example, you can map `jamal = jamal <jamal>` to `jamal = Jamal Hartnett <[email protected]>`.
Copy file name to clipboardexpand all lines: docs/artifacts/quickstarts/python-packages.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ If you have a Visual Studio Enterprise license, you already have access to Packa
49
49
On your first visit to Azure Artifacts, you're welcomed with an image that prompts you to create a new feed. Select the **+ New feed** button.
50
50
51
51
In the dialog box:
52
-
***Name**: Give the feed a name. "PyPI" is the default repository name for `twine`, which is a tool for publishing Python packages. We recommend that you don't name your feed "PyPI," because you might accidently push to the wrong repository if you don't provide a repository name with `-r`.
52
+
***Name**: Give the feed a name. "PyPI" is the default repository name for `twine`, which is a tool for publishing Python packages. We recommend that you don't name your feed "PyPI," because you might accidentally push to the wrong repository if you don't provide a repository name with `-r`.
53
53
***Visibility**: Choose who can read and contribute (or update) packages in your feed. An organization-visible feed is created with permissions that allow all users in the organization to see and use your feed (recommended). A private feed is created with permissions such that only you have access.
54
54
***Packages from public sources**: Selecting **Use packages from public sources through this feed** will add the public npm, NuGet, and PyPI registries as upstreams to your feed. When upstreams are enabled, your client will be able to fetch packages from the public registry through your private feed, and your private feed will cache those packages for you. If you select **Use packages published to this feed**, your feed will be created without connectivity to public registries. You can connect them later if you want.
55
55
* When you're done, select **Create**.
@@ -96,7 +96,7 @@ To learn more about how to create, configure, and use Python packages as part of
96
96
97
97
## Resources
98
98
99
-
If you’d like to learn more about how Python packages work, there’s a great writeup in the *Architecture of Open Source Applications* book. Here's an excerpt:
99
+
If you’d like to learn more about how Python packages work, there’s a great write-up in the *Architecture of Open Source Applications* book. Here's an excerpt:
100
100
101
101
*[The Architecture of Open Source Applications: Python Packaging](http://www.aosabook.org/en/packaging.html)
Copy file name to clipboardexpand all lines: docs/boards/queries/linking-attachments.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@ For Azure Boards (cloud service), you can add up to 100 attachments to a work it
261
261
<tr>
262
262
<td><aid="related-link-count"/>
263
263
<p>Related Link Count</p></td>
264
-
<td><p>The number of links defined for a work item which use a work link type, such as Parent-Child, Predecessor-Sucessor, and Related. For a full list, see [Link type reference](link-type-reference.md#work-link-types)</p>
264
+
<td><p>The number of links defined for a work item which use a work link type, such as Parent-Child, Predecessor-Successor, and Related. For a full list, see [Link type reference](link-type-reference.md#work-link-types)</p>
265
265
<p>Reference Name=System.RelatedLinkCount, Data type=Integer</p>
Copy file name to clipboardexpand all lines: docs/extend/_shared/manifest-core.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,5 +8,5 @@ These properties are required:
8
8
|**version**|*A string specifying the version of an extension.*| Should be in the format `major.minor.patch`, for example `0.1.2` or `1.0.0`. You can also add a fourth number for the following format: `0.1.2.3`|
9
9
|**name**|*A short, human-readable name of the extension. Limited to 200 characters.*| Example: `"Fabrikam Agile Board Extension"`. |
10
10
|**publisher**|*The identifier of the publisher.*| This identifier must match the identifier the extension is published under. See [Create and manage a publisher](../publish/overview.md). |
11
-
| **categories** | *Array of strings representing the categories your extension belongs to. At least one category must be provided and there is no limit to how many categories you may include.* | Valid values: `Azure Repos`, `Azure Boards`, `Azure Pipelines`, `Azure Test Plans`, and `Azure Artifacts`.<br/><br/>Notes:<ul><li>Use version >=0.6.3 of the tfx-cli if you are publishing the extension programmatically. </li><li>If using [Azure DevOps Extension Tasks extension](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-developer-tools-build-tasks) to publish then ensure that its version is >= 1.2.8 (you may need to approve the extension update due to recent scope changes).</li><li>The categories mentioned above are natively present in Visual Studio Marketplace and Azure DevOps Server 2019 & above. For extensions targetting earlier versions of Team Foundation Server (i.e. TFS <= 2018):<ul><li> If the TFS customers would be acquiring your extension via Visual Studio Marketplace (not local gallery) in connected context then leverage the categories stated above. </li><li> If you are going to share the extension directly (i.e. not via the Visual Studio Marketplace) with a customer using TFS <=2018 then leverage the following categories instead: Code, Plan and track, Build and release, Test, Collaborate, and Integrate. If your need is to share both via Visual Studio Marketplace and directly with a TFS <= 2018 customer then you would need to have 2 extension packages.</li></ul></ul>|
11
+
| **categories** | *Array of strings representing the categories your extension belongs to. At least one category must be provided and there is no limit to how many categories you may include.* | Valid values: `Azure Repos`, `Azure Boards`, `Azure Pipelines`, `Azure Test Plans`, and `Azure Artifacts`.<br/><br/>Notes:<ul><li>Use version >=0.6.3 of the tfx-cli if you are publishing the extension programmatically. </li><li>If using [Azure DevOps Extension Tasks extension](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-developer-tools-build-tasks) to publish then ensure that its version is >= 1.2.8 (you may need to approve the extension update due to recent scope changes).</li><li>The categories mentioned above are natively present in Visual Studio Marketplace and Azure DevOps Server 2019 & above. For extensions targeting earlier versions of Team Foundation Server (i.e. TFS <= 2018):<ul><li> If the TFS customers would be acquiring your extension via Visual Studio Marketplace (not local gallery) in connected context then leverage the categories stated above. </li><li> If you are going to share the extension directly (i.e. not via the Visual Studio Marketplace) with a customer using TFS <=2018 then leverage the following categories instead: Code, Plan and track, Build and release, Test, Collaborate, and Integrate. If your need is to share both via Visual Studio Marketplace and directly with a TFS <= 2018 customer then you would need to have 2 extension packages.</li></ul></ul>|
12
12
|**targets**|*The products and services supported by your integration or extension.* See [installation targets](../develop/manifest.md#installation-targets) for more details. | This is an array of objects, where each object has an `id` field indicating one of the following: <ul><li>`Microsoft.VisualStudio.Services` (extensions that works with Azure DevOps Services or TFS),</li><li> `Microsoft.TeamFoundation.Server` (extension that works with TFS),</li><li> `Microsoft.VisualStudio.Services.Integration` (integrations that works with Azure DevOps Services or TFS), </li><li>`Microsoft.TeamFoundation.Server.Integration` (integrations that work with TFS)</li></ul> |
Copy file name to clipboardexpand all lines: docs/extend/_shared/procedures/publish-app-iis.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -4,22 +4,22 @@
4
4
5
5
3. Publish your web app from the solution explorer.
6
6
7
-
7
+
8
8
9
9
4. Use the custom target.
10
10
11
-
11
+
12
12
13
13
4. Set the connection info.
14
14
15
-
15
+
16
16
17
17
Verify that and then step through the rest of the publish wizard.
18
18
19
19
5. In the IIS Manager, select your web site and add an HTTPs binding if you don't already have one.
20
20
21
-
21
+
22
22
23
23
6. Open SSL Settings to require SSL for your web site.
24
24
25
-
25
+
Copy file name to clipboardexpand all lines: docs/extend/develop/add-build-task.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -374,7 +374,7 @@ tsc
374
374
mocha tests/_suite.js
375
375
```
376
376
377
-
Both tests should pass. If you want to run the tests with more verbose output (what you would see in the build console), set the environment variable: ```TAST_TEST_TRACE=1```:
377
+
Both tests should pass. If you want to run the tests with more verbose output (what you would see in the build console), set the environment variable: ```TASK_TEST_TRACE=1```:
*`keySelector`: string. An Json based keyselector to filter response returned by fetching the endpoint Url.A Json based keyselector must be prefixed with "jsonpath:". KeySelector can be used to specify the filter to get the keys for the values specified with Selector. The following keyselector defines an Json for extracting nodes named 'ServiceName'. endpoint.KeySelector = "jsonpath://ServiceName";
24
24
25
-
*`scope`: string. The scope as understood by Connected Services. Essentialy, a project-id for now.
25
+
*`scope`: string. The scope as understood by Connected Services. Essentially, a project-id for now.
26
26
27
27
*`selector`: string. An XPath/Json based selector to filter response returned by fetching the endpoint Url. An XPath based selector must be prefixed with the string "xpath:". A Json based selector must be prefixed with "jsonpath:". The following selector defines an XPath for extracting nodes named 'ServiceName'. endpoint.Selector = "xpath://ServiceName";
0 commit comments