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
Merged PR 405232: Manual sync public changes to private
This PR brings in customer (and some internal) PRs that were reviewed, approved, and merged into the public repo that didn't get synced back to the private repo. See the commits list for the PRs, unfortunately there doesn't seem to be a way to get from the files in the files view to the associated commit and commit message (which is the link to the PR). All changes in this current PR have been reviewed and approved over on the public repo - this review is just a sanity check.
Copy file name to clipboardexpand all lines: docs/_shared/help-support-shared.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,6 @@
4
4
5
5
We welcome your feedback.
6
6
7
-
For product related inquiries, review our [User Voice page](https://visualstudio.uservoice.com/forums/330519-team-services) or report a problem at [Developer Community](https://developercommunity.visualstudio.com/spaces/21/index.html). Also, you can get advice on [Stack Overflow](https://stackoverflow.com/questions/tagged/vsts), or get support via our [Support](https://azure.microsoft.com/support/devops/) page.
7
+
For product related inquiries, review our [User Voice page](https://visualstudio.uservoice.com/forums/330519-team-services) or report a problem at [Developer Community](https://developercommunity.visualstudio.com/spaces/21/index.html). Also, you can get advice on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-devops), or get support via our [Support](https://azure.microsoft.com/support/devops/) page.
8
8
9
9
Follow us on **[Twitter](https://twitter.com/AzureDevOps)@AzureDevOps**.
**Important for Visual Studio subscribers and Visual Studio Dev Essentials members**:
18
18
19
-
* You can't use [monthly credits for Visual Studio subscriptions](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/)
20
-
or [monthly credits for Visual Studio Dev Essentials](https://azure.microsoft.com/en-us/offers/ms-azr-0022p/) to pay for Azure DevOps purchases.
19
+
* You can't use [monthly credits for Visual Studio subscriptions](https://azure.microsoft.com/pricing/member-offers/msdn-benefits-details/)
20
+
or [monthly credits for Visual Studio Dev Essentials](https://azure.microsoft.com/offers/ms-azr-0022p/) to pay for Azure DevOps purchases.
21
21
You can still use these types of Azure subscriptions for billing,
22
22
but the monthly credits won't apply, so your credit card will be billed for charges instead.
23
23
24
-
* Before you use these Azure subscriptions for billing, you must remove their [default spending limit indefinitely](https://azure.microsoft.com/en-us/pricing/spending-limits/).
24
+
* Before you use these Azure subscriptions for billing, you must remove their [default spending limit indefinitely](https://azure.microsoft.com/pricing/spending-limits/).
25
25
26
26
This prevents disabling your Azure subscription
27
27
when your monthly charges are billed the next month.
Copy file name to clipboardexpand all lines: docs/articles/migration-post-import.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ An Azure DevOps organization is ready for use once an import has completed succe
22
22
## Immediately After Import
23
23
Immediately after the organization becomes available you will want to take a small team and perform spot checks on the organization. It's recommended that this team consists of the project collection administrators. This shouldn't be an in-depth check, but rather making sure that major pieces from your collection were brought over. Did your source code get imported? Are you seeing your build history? Are all of our area paths still present? It's best to confirm these artifacts are present before opening the organization to the entirety of your user base.
24
24
25
-
After spot checking the organization you will want to consider if you want to rename it. [Renaming an Azure DevOps organization](../organizations/accounts/rename-organization.md) is a simple operation, but it has [large impacts](https://support.microsoft.com/en-us/kb/2793597) on users currently using the organization. Some examples being Team Explore connections breaking or bookmarks no longer working. Getting a rename out of the way while it's just a small group of users using the organization allows the rest of the users to come in and configure their connections once.
25
+
After spot checking the organization you will want to consider if you want to rename it. [Renaming an Azure DevOps organization](../organizations/accounts/rename-organization.md) is a simple operation, but it has [large impacts](https://support.microsoft.com/kb/2793597) on users currently using the organization. Some examples being Team Explore connections breaking or bookmarks no longer working. Getting a rename out of the way while it's just a small group of users using the organization allows the rest of the users to come in and configure their connections once.
26
26
27
27
## Set up Billing
28
28
@@ -39,7 +39,7 @@ This means that you shouldn't have to take any other import steps if your identi
39
39
Dry run imports do not have their licenses reset on the 1st of the month. Unlike production imports, their grace period extends for the life of the organization. So you don't need to worry about purchasing licenses while testing out an import.
40
40
41
41
## Builds
42
-
Next, you will want to configure your build agents. As part of the migration, all of your build pipelines have been brought over, but agents and pools need to be reconfigured against the new Azure DevOps organization. Azure DevOps Services offers the ability to use a Microsoft-hosted pool of build agents that you can use, or you can connect your self-hosted build agent(s). It's important to note that only one self-hosted build agent is included for free. After that there is a [fee](https://visualstudio.microsoft.com/en-us/products/visual-studio-team-services-pricing-vs.aspx) for having additional self-hosted build agents. To pay for Microsoft-hosted and self-hosted build agents you will need to link a subscription to your Azure DevOps organization. See the following resources for details on performing this task:
42
+
Next, you will want to configure your build agents. As part of the migration, all of your build pipelines have been brought over, but agents and pools need to be reconfigured against the new Azure DevOps organization. Azure DevOps Services offers the ability to use a Microsoft-hosted pool of build agents that you can use, or you can connect your self-hosted build agent(s). It's important to note that only one self-hosted build agent is included for free. After that there is a [fee](https://visualstudio.microsoft.com/products/visual-studio-team-services-pricing-vs.aspx) for having additional self-hosted build agents. To pay for Microsoft-hosted and self-hosted build agents you will need to link a subscription to your Azure DevOps organization. See the following resources for details on performing this task:
Copy file name to clipboardexpand all lines: docs/articles/migration-troubleshooting.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ The largest table size is currently {Table size}GBs. This is above the recommend
36
36
Similar to the previous warning, this warning means you will have to use the SQL Azure VM method to complete the import. Follow the instructions linked from the warning message to setup the VM and complete your import. This warning does **NOT** mean that your collection is too big to be imported.
37
37
38
38
```cmdline
39
-
The database metadata size is currently {Metadata Size}GBs. This is above the recommended size of {Warning Size}GBs. It's recommended that you consider cleaning up older data as described in [Cleaning up old data](/tfs/server/upgrade/clean-up-data).
39
+
The database metadata size is currently {Metadata Size}GBs. This is above the recommended size of {Warning Size}GBs. It's recommended that you consider cleaning up older data as described in [Cleaning up old data](/tfs/server/upgrade/clean-up-data).
40
40
```
41
41
42
42
This warning means that your database is approaching the limit for total metadata size. Metadata size refers to the size of your database without including files, code, and other binary data. The warning does **NOT** mean that your collection is too big for import, rather its metadata size is larger than the vast majority of other databases. It's strongly recommended that you [reduce the size](/tfs/server/upgrade/clean-up-data) of your database before import. Reducing the size provides the additional benefit of speeding up your import.
@@ -118,13 +118,13 @@ ISVError:100014 Missing permission for group:Microsoft.TeamFoundation.Identity;S
If you have multiple errors that need to be corrected, it's recommended that you put all of the commands into a batch file to execute them against TFSSecurity in an automated fashion. Once the commands have been executed you will need to run TfsMigrator validate again to ensure that the error(s) has\have been corrected. If the error(s) still persists, please contact [Azure DevOps Services customer support](https://aka.ms/AzureDevOpsImportSupport).
Copy file name to clipboardexpand all lines: docs/articles/phase-rollout-with-rings.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ monikerRange: '>= tfs-2013'
16
16
17
17
In today's fast-paced, feature-driven markets, it's important to continuously deliver value and receive feedback on features quickly and continuously. Partnering with end users to get early versions of features vetted out is valuable.
18
18
19
-
Are you planning to build and deploy Azure DevOps extensionsto production? You probably have a few questions, such as:
19
+
Are you planning to build and deploy Azure DevOps extensions to production? You probably have a few questions, such as:
20
20
* How do you embrace DevOps to deliver changes and value faster?
21
21
* How do you mitigate the risk of deploying to production?
22
22
* How do you automate the build and deployment?
@@ -58,7 +58,7 @@ Next you need to map the topology of your application to the ringed deployment m
58
58
> The ringed deployment model is not a silver bullet!
59
59
> Start small, prototype, and continuously compare impact, value, and cost.
60
60
61
-
At the application level, the composition of Azure DevOps extensionsis innocuous, easy to digest, scale, and deploy independently. Each extension:
61
+
At the application level, the composition of Azure DevOps extensions is innocuous, easy to digest, scale, and deploy independently. Each extension:
62
62
* Has one of more web and script files
63
63
* Interfaces with Core client
64
64
* Interfaces with REST client and REST APIs
@@ -83,7 +83,7 @@ The extension topology is perfectly suited for the ring deployment model and to
83
83
84
84
Let's observe how a change triggers and moves through the ring-based deployment process, using the [Azure DevOps Developer Tools Build Tasks](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-developer-tools-build-tasks) extension.
85
85
86
-
**Azure DevOps Developer Tools Build Tasks** extension is the secret sauce, used to package and publish Azure DevOps extensionsto the Visual Studio Marketplace.
86
+
**Azure DevOps Developer Tools Build Tasks** extension is the secret sauce, used to package and publish Azure DevOps extensions to the Visual Studio Marketplace.
@@ -171,7 +171,7 @@ Refer to [Default and custom release variables](/azure/devops/pipelines/release/
171
171
172
172
### How can you manage secrets used by the pipeline?
173
173
174
-
Refer to [Azure Key Vault](https://azure.microsoft.com/en-us/services/key-vault/) to safeguard cryptographic keys and other secrets used by your pipelines.
174
+
Refer to [Azure Key Vault](https://azure.microsoft.com/services/key-vault/) to safeguard cryptographic keys and other secrets used by your pipelines.
0 commit comments