Merge pull request #2569 from MicrosoftDocs/main

Deprecation announcement
PatGet · Mar 14, 2024 · 8c4a411 · 8c4a411
2 parents 3a02074 + f904f18
commit 8c4a411
Show file tree

Hide file tree

Showing 299 changed files with 620 additions and 20 deletions.
diff --git a/docs/TOC.md b/docs/TOC.md
@@ -1,5 +1,6 @@
 # [App Center Overview](index.yml)
 
+# [App Center Retirement](retirement.md)
 # [Help & Feedback](help.md)
 
 # General

diff --git a/docs/analytics/event-metrics.md b/docs/analytics/event-metrics.md
@@ -12,6 +12,9 @@ ms.custom: analytics
 ---
 
 # Events Metrics
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 Events are actions that users take in your app. By tracking events in your app, you'll learn more about your users' behavior and understand the interaction between your users and your apps. Attaching properties to your events will provide you with contextual information about the events.
 
 Tracking events in your app allows you to answer questions like:

diff --git a/docs/analytics/export.md b/docs/analytics/export.md
@@ -12,6 +12,8 @@ ms.custom: analytics
 ---
 
 # Export
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
 
 App Center allows you to continuously export all your Analytics raw data into Azure. You can export Analytics data to both [Blob Storage](https://azure.microsoft.com/services/storage/blobs/) and [Application Insights (Azure Monitor)](/azure/azure-monitor/app/app-insights-overview).
 By exporting the data, you benefit from:

diff --git a/docs/analytics/faq.md b/docs/analytics/faq.md
@@ -12,6 +12,9 @@ ms.custom: analytics
 ---
 
 # Analytics FAQ
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 ## Is the data sampled?
 The data isn't sampled. Analytics will use all the data that's sent, unless it's sent in the wrong format or some of the known limits are reached.
 

diff --git a/docs/analytics/handled-errors-events.md b/docs/analytics/handled-errors-events.md
@@ -12,6 +12,9 @@ ms.custom: analytics
 ---
 
 # How to Use Events for Handled Errors
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 > [!IMPORTANT]
 > Handled Errors aren't available yet as part of the Crashes service in App Center. One workaround is to use Custom Events. This isn't how "Handled Errors" are intended to be supported and it isn't the main purpose of Events either. However, this page contains advice on how to best use Events to report on handled errors.
 

diff --git a/docs/analytics/index.md b/docs/analytics/index.md
@@ -11,7 +11,9 @@ ms.service: vs-appcenter
 ms.custom: analytics
 ---
 
-# Analytics
+# Analytics 
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
 
 App Center Analytics will help you understand more about your app users and their behavior when using your app.
 

diff --git a/docs/analytics/log-flow.md b/docs/analytics/log-flow.md
@@ -12,6 +12,8 @@ ms.custom: analytics
 ---
 
 # Log Flow
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
 
 Log Flow will show you what's being received by the backend in real time. The main use cases for log flow are:
 

diff --git a/docs/analytics/overview.md b/docs/analytics/overview.md
@@ -12,6 +12,9 @@ ms.custom: analytics
 ---
 
 # Overview Page
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 
 The goal of the Overview page is to provide you with the key metrics about your app users. This includes their devices, location, activity, and engagement. This allows you to answer questions such as:
 

diff --git a/docs/api-docs/index.md b/docs/api-docs/index.md
@@ -13,6 +13,8 @@ ms.custom: api
 
 # App Center API Documentation
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 ## App Center OpenAPI Specification (Swagger)
 App Center exposes a full set of API endpoints. You can explore the App Center API through the [App Center OpenAPI Specification](https://openapi.appcenter.ms).
 

diff --git a/docs/build/android/code-signing.md b/docs/build/android/code-signing.md
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: android
 ---
 
 # Android code signing setup in App Center
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 > [!TIP]
 > For Xamarin.Android users, the process is slightly different. See our [Xamarin.Android Code Signing guide](~/build/xamarin/android/code-signing.md) for details.
 

diff --git a/docs/build/android/index.md b/docs/build/android/index.md
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: android
 ---
 
 # Building Java apps for Android
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 To build your first Android app, follow these steps:
 
 1. Connect to your repository service account (GitHub, Bitbucket, VSTS, Azure DevOps).

diff --git a/docs/build/android/jcentershut.md b/docs/build/android/jcentershut.md
@@ -3,7 +3,7 @@ title: If Build fails at getting JCenter Bintray resources
 description: How to deal with JCenter shutdown
 keywords: android
 author: milenkomarkovic
-ms.author: v-gorad
+ms.author: v-gradojcic
 ms.date: 06/16/2021
 ms.topic: article
 ms.assetid: 
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: android
 ---
 
 # Gradle build after JCenter shutdown
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 If you use JCenter and Bintray resources in your AppCenter Android builds and your builds fail on Gradle Task failure (could not get resource error), it's because JCenter Bintray is being shut down.
 Following lines (from Build Logs) illustrate this problem:
 

diff --git a/docs/build/branches.md b/docs/build/branches.md
@@ -13,6 +13,8 @@ ms.assetid: 392b1718-cdb2-4831-a20a-d7d6eccc0e96
 
 # Branches and build configurations
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 After you [connect your repository](~/build/connect.md), you can configure continuous integration for any of your repository's branches.
 In App Center Build, your branches are the origin of setting up a build. For every branch you can configure whether you want to build on every push, or only when you manually queue a build.
 

diff --git a/docs/build/build-test-integration.md b/docs/build/build-test-integration.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Testing Builds on Real Devices
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 In this document, you'll learn how to integrate App Center Build and [App Center Test](~/test-cloud/index.md) to run your latest successful build on real devices. 
 
 ## Supported Configurations

diff --git a/docs/build/build-to-store.md b/docs/build/build-to-store.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Distributing a build to the store
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 In this document, you'll learn how to distribute your build to a store. You can get your completed app to the store directly from App Center.
 
 ## Automatically distribute from your branch configuration

diff --git a/docs/build/choose-between-services.md b/docs/build/choose-between-services.md
@@ -11,6 +11,9 @@ ms.service: vs-appcenter
 ---
 
 # Choose the right service for app builds
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 The choice on whether to use [Visual Studio App Center](https://visualstudio.microsoft.com/app-center/) or [Azure Pipelines](https://azure.microsoft.com/services/devops/pipelines/) requires some thought. There are some scenarios where one service might suit your needs better than the other.  
 
 The following questions should help you make an informed decision on which service works best for you. 

diff --git a/docs/build/connect.md b/docs/build/connect.md
@@ -12,6 +12,9 @@ ms.assetid: 1EFB8DFD-76D5-4F8C-B73A-2CFBE3E3BD97
 ---
 
 # Managing source repository connections
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 App Center supports connections to the following code repository services: [Bitbucket](https://bitbucket.org/), [GitHub](https://github.com/), [Gitlab.com](https://gitlab.com), and [Azure DevOps (formerly VSTS)](https://visualstudio.microsoft.com/team-services/). Build apps in App Center by connecting to one of these providers. Please note that SSH connection is not supported.
 
 > [!NOTE]

diff --git a/docs/build/custom/dependencies/index.md b/docs/build/custom/dependencies/index.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Custom Build Dependency Handling
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 > [!NOTE] 
 > Issues you find with custom dependency handling are generally beyond the scope of App Center support, because it's infeasible to QA highly custom functionality.
 

diff --git a/docs/build/custom/scripts/index.md b/docs/build/custom/scripts/index.md
@@ -12,6 +12,10 @@ ms.custom: build
 ---
 
 # Build scripts
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
+
 > [!NOTE]
 > Build scripts allow you to customize your builds; but issues you find during that process are beyond the scope of App Center support. If one of your scripts is failing, the whole build will report a failure, even if the primary build up to that point were successful.
 

diff --git a/docs/build/custom/variables/index.md b/docs/build/custom/variables/index.md
@@ -12,6 +12,10 @@ ms.custom: build
 ---
 
 # Build Environment variables
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
+
 Environment variables help manage your [build script tasks](~/build/custom/scripts/index.md). You can call pre-defined variables or create your own.
 
 ## Pre-Defined variables

diff --git a/docs/build/export-to-azure-pipelines.md b/docs/build/export-to-azure-pipelines.md
@@ -13,6 +13,8 @@ ms.assetid: 808F6809-E2B0-4D45-A674-DFE4B5652A94
 
 # Export App Center Build configuration to Azure Pipelines
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 ## Overview
 With App Center, you can export all of your App Center Build configurations to Azure Pipelines using the Build export feature. You can download JSON or YAML file and import it into Azure Pipelines.
 

diff --git a/docs/build/github-app.md b/docs/build/github-app.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Connecting Repositories Using the GitHub App
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 In this document, you'll learn how to install the App Center GitHub app and use this integration in your development workflow.
 
 ## Installing the App Center GitHub App

diff --git a/docs/build/index.md b/docs/build/index.md
@@ -13,6 +13,8 @@ ms.custom: build
 
 # App Center Build
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 The App Center Build service helps you build Android, iOS, macOS, and UWP apps using a secure cloud infrastructure. Connect to your repo in App Center and start building your app in the cloud on every commit. With Build you can forget about configuring build servers locally, complicated configurations, and code that builds on a coworker's machine but not yours.
 
 With App Center's other services, you can further automate your workflow: 

diff --git a/docs/build/ios/code-signing.md b/docs/build/ios/code-signing.md
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: ios
 ---
 
 # Code signing for iOS
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 iOS apps must be signed to run on real devices. In App Center, this process requires uploading valid signing files generated using [Apple's code signing process](https://developer.apple.com/support/code-signing/). You must be able to successfully sign a valid app package locally before attempting to in App Center. 
 
 ## Signing files

diff --git a/docs/build/ios/index.md b/docs/build/ios/index.md
@@ -13,6 +13,10 @@ ms.tgt_pltfrm: ios
 ---
 
 # Building Objective-C or Swift apps for iOS
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
+
 To build your first native iOS app, you must take the following actions:
 
 1. Connect to your repository service account (GitHub, Bitbucket, VSTS, Azure DevOps)

diff --git a/docs/build/macos/code-signing.md b/docs/build/macos/code-signing.md
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: macos
 ---
 
 # Code signing for macOS
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 An app must be signed to pass the [macOS Gatekeeper](https://support.apple.com/HT202491) and to submit an app to the App Store. Sign a build by uploading your provisioning profile `.provisionprofile` and certificate `.p12` when [configuring the build](index.md). On macOS, provisioning profiles are optional depending on whether your project is using sandboxing or not. Once you've saved a provisioning profile and the matching certificate to a build configuration of a branch, App Center will sign your app with the provided assets whatever the settings of your project. When you provide a certificate only, it must match the project settings, otherwise it will fail.
 
 Learn more about where to [find the provisioning profiles and certificates](#uploading-code-signing-files) that are required for signing. When **Automatically manage signing** is enabled in the target of your project, it's possible to upload the developer provisioning profile generated by Xcode instead of one from the Apple Developer Portal.

diff --git a/docs/build/macos/index.md b/docs/build/macos/index.md
@@ -13,6 +13,9 @@ ms.tgt_pltfrm: macos
 ---
 
 # Building Objective-C or Swift apps for macOS
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 To start building your first Mac app, do these steps:
 
 1. Connect to your repository service account (GitHub, Bitbucket, VSTS, Azure DevOps).

diff --git a/docs/build/notifications.md b/docs/build/notifications.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Build Notifications
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 Email and custom webhook notifications give you continual real-time updates of your build status, as well as the permanency and ability to search and be directed to your builds in App Center. These notifications enable faster collaboration, since you can forward the build status emails or @ mention collaborators in a single workflow.
 
 You can choose to have email and webhook notifications automatically sent for the following events:

diff --git a/docs/build/react-native/Android/index.md b/docs/build/react-native/Android/index.md
@@ -14,6 +14,8 @@ ms.tgt_pltfrm: react-native
 
 # Building React Native apps for Android
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 App Center can build React Native apps using React Native version 0.34 or newer.
 
 To start building your first React Native Android app, you must:

diff --git a/docs/build/react-native/iOS/index.md b/docs/build/react-native/iOS/index.md
@@ -13,6 +13,10 @@ ms.tgt_pltfrm: react-native
 ---
 
 # Configure a React Native iOS build in App Center
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
+
 App Center can build React Native apps written in React Native version 0.34 or newer.
 
 To build a React Native app for iOS:

diff --git a/docs/build/react-native/index.md b/docs/build/react-native/index.md
@@ -14,6 +14,8 @@ ms.tgt_pltfrm: react-native
 
 # React Native Build
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 You can build React Native apps for both Android and iOS. To get started, use the following links:
 
 - [Configuring your first Android build](~/build/react-native/android/index.md)

diff --git a/docs/build/react-native/nodejs.md b/docs/build/react-native/nodejs.md
@@ -14,6 +14,8 @@ ms.tgt_pltfrm: react-native
 
 # Node.js selection
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 ## Major versions of Node.js
 The following versions are available for use in App Center Build: 6.X, 8.x, 10.x, 12.x, 14.x, 16.X.
 See Also: [App Center Cloud Build Machines](~/build/software.md)

diff --git a/docs/build/software.md b/docs/build/software.md
@@ -13,6 +13,8 @@ ms.custom: build
 
 # App Center Cloud Build Machines
 
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 Each build runs on a separate, clean virtual machine (VM) no one else has access to. Once the build completes, App Center discards the virtual machine, and all files removed. The artifacts resulting from the build (log files, application files, symbol files) are stored on App Center servers.
 
 ## Operating System

diff --git a/docs/build/troubleshooting/backup-data.md b/docs/build/troubleshooting/backup-data.md
@@ -11,6 +11,9 @@ ms.custom: build
 ---
 
 # Backing up Build data
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 Build data in App Center is kept for 30 days after creation. However, it can also be deleted before 30 days have passed in two ways:
 
 - The configuration for the branch in App Center is deleted, which erases all data for that branch.

diff --git a/docs/build/troubleshooting/build-command.md b/docs/build/troubleshooting/build-command.md
@@ -11,6 +11,9 @@ ms.custom: build
 ---
 
 # How to find your build command in App Center
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 Sometimes it's useful to compare the exact build command executed across different builds. 
 
 To compare commands, it helps to know where to look in App Center's logs. What the commands look like and how to find them depends your app's framework. 

diff --git a/docs/build/troubleshooting/build-failed.md b/docs/build/troubleshooting/build-failed.md
@@ -11,6 +11,9 @@ ms.custom: build
 ---
 
 # Failed builds
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 There are various reasons why your build could have failed that might be unique to your project. Usually an efficient way to diagnose build failures is comparing them to a working build. This process can minimize variables and identify relevant conditions for your scenario. 
 
 ## If building works locally but not in App Center

diff --git a/docs/build/troubleshooting/build-times.md b/docs/build/troubleshooting/build-times.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Understanding Build Execution Time
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 There are many reasons why build duration can be higher when using App Center Build:
 
 * When running your build locally, many things are cached, including NuGet packages, pods, dependencies, and so on. In App Center, we always do a clean build, and also redownload dependencies not already included in your repository.

diff --git a/docs/build/troubleshooting/code-repos.md b/docs/build/troubleshooting/code-repos.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Code Repository Troubleshooting
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 ## Repository isn't listed in the Connect to Repository step
 * **Only Git repositories are supported**. Other repository types like Mercurial, TFVC, and so on, won't show up in the repository list.
 * **Connecting to a user-owned repository must be done by the owner**. If you aren't the owner, you can still onboard the app by inviting the repository owner as a collaborator in App Center. Then, the owner can connect the repository as a source to the App Center build service.

diff --git a/docs/build/troubleshooting/index.md b/docs/build/troubleshooting/index.md
@@ -12,6 +12,9 @@ ms.custom: build
 ---
 
 # Build Troubleshooting
+
+[!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
+
 The guides in this section provide general troubleshooting tips for App Center Build.
 
 ## General Tips
-Original file line number
+Diff line change
@@ Expand Up / @@ -12,6 +12,8 @@ ms.custom: analytics @@
     ---
     # Log Flow
+    [!INCLUDE [Retirement announcement for App Center](~/includes/retirement.md)]
     Log Flow will show you what's being received by the backend in real time. The main use cases for log flow are:
@@ Expand Down @@