Remove content on using auto detected deploy markers (#9442)

* remove content on using auto detected deploy markers

* formatting

Author: rosieyohannan

jekyll/_cci2/deploy/configure-deploy-markers.adoc

@@ -12,13 +12,9 @@ contentTags:
 
 This tutorial shows how to add a deploy marker step to your workflow config. Deploy markers allow you to log all new deployments in one place, update their status and link back to the CI/CD pipelines that triggered them.
 
-Unless you opt out of the feature, CircleCI autodetects potential deployments and creates deploy markers for you.
-
-This guide is for you if you would rather create deploy markers yourself. For more information see the xref:deploys-overview#[Deploys overview] page.
-
 == Introduction
 
-Autodetected or manually configured deploy markers provide a lightweight way to log your deployments without requiring a you to install the CircleCI release agent. If you install deploy markers manually, as described in this guide you will also be able to use the xref:set-up-rollbacks#[CircleCI rollback feature].
+Deploy markers provide a lightweight way to log your deployments without requiring a you to install the CircleCI release agent. If you install deploy markers, as described in this guide, you will also be able to use the xref:set-up-rollbacks#[CircleCI rollback feature].
 
 For a full guide to CircleCI's deploys features and functionality, refer to the xref:set-up-circleci-deploys#[Set up CircleCI deploys] guide.
 

jekyll/_cci2/deploy/deploys-overview.adoc

@@ -294,75 +294,28 @@ The following table shows a complete list of labels and annotations either requi
 |No. Only set if you want to disable the cancel deployment feature for your component.
 |===
 
-== Automatic deployment detection and deploy markers
+== Deploy markers
 
-CircleCI automatically generates deploy markers for your deployment pipelines. Deploy markers provide a lightweight way to log your deployments without requiring a full CircleCI deploys setup. Deploy markers generate a log of all deployments in one place, for a clear overview of what has changed, without the need to search through your CI/CD pipelines. Deploy markers log all new deployments in one place and link back to the CI/CD pipelines that caused them. You can use deploy markers independently, without installing the CircleCI release agent.
+Deploy markers provide a lightweight way to log your deployments without requiring a full CircleCI deploys setup. Deploy markers generate a log of all deployments in one place, for a clear overview of what has changed, without the need to search through your CI/CD pipelines. Deploy markers log all new deployments in one place and link back to the CI/CD pipelines that caused them.
 
-=== Automatic detection of deployments
+See the xref:configure-deploy-markers#[Configure deploy markers] page for full setup details.
 
-CircleCI looks for the word `deploy` in your job names to detect when a deployment may have happened and creates an auto-detected deploy marker.
+=== Manual configuration of automatically detected deploys
 
-When CircleCI creates a deploy marker for you automatically, we use the information available in your pipeline configuration to create the following:
+If you have some link:https://circleci.com/changelog/auto-generated-deploy-markers-are-being-sunset/[automatically detected deploy markers] you can consider manually configuring them. CircleCI no longer automatically creates deploy markers for you.
 
-* **Component**: CircleCI created a component for the deployment and uses your project name to create a component name.
-* **Environment integration**: CircleCI creates an environment for you, using your job and workflow names to attempt to create a relevant name. If an environment name cannot be generated, the name will be `autogenerated`, and you can edit it later. The environment has the type `AUTODETECTED`.
-* **Version**: CircleCI uses the build number to populate the version for the purposes of displaying the deployment in the CircleCI web app.
-
-If any of the following conditions are true, CircleCI **will not** automatically generate a deploy marker for a job even if the name contains the word `deploy`:
-
-* The job has a status other than `SUCCESS`.
-* Any of the following keywords and keyword combinations are present in the job name:
-** `dry run`
-** `skip deploy`
-** `bypass deploy`
-** `deployed`
-** `validation`
-** `validate`
-* The project related to the job has deployments created via the Kubernetes release agent or manual release-type jobs in the last two months.
-* You have opted out of the automatic deploy detection feature.
-* The detected environment integration name collides with an integration you have already set up.
-
-==== Manual configuration of automatically detected deploys
 Some points to consider when manually configuring an automatically detected deploy are as follows:
 
-* If you decide you would like to manually configure a deploy marker for an environment integration that was created as part of an automatically detected deploy, refer to the xref:configure-deploy-markers#[Configure deploy markers] page to set up a deploy marker and a new environment integration.
-
 * If you change a component name that was originally autodetected by CircleCI, we create a new component and the history **will not** carry over. If you do not update the component name, the history **will** carry over.
 
 * If your environment integration has an autogenerated name, you can edit the name as follows:
-.. In the link:https://circleci.com/app/home[CircleCI web app], select your organization.
-.. Select **Deploys** in the sidebar.
-.. Select the **Environments** tab.
-.. Find your environment and select cog icon (icon:cog[]) to enter the environment integration settings page.
-.. Select **Edit**.
-.. Enter a new name and select btn:[Update].
-
-
-=== Opt out of automatic deploy detection
-If you do not want CircleCI to automatically create deploy markers for you, you can opt out of this feature either for a whole organization or per-project.
-
-To opt out of automatic deploy detection for an entire **organization**, follow these steps:
-
-. In the link:https://circleci.com/app/home[CircleCI web app], select your organization.
-. Select **Organization settings** in the sidebar.
-. Select **Deploys**.
-. Toggle the "Enable automatic deploy marker detection" option left. You will see a confirmation message in the bottom right hand corner of the app. To re-enable the feature, toggle the option to the right.
-
-To opt out of automatic deploy detection for a **project**, follow these steps:
-
++
 . In the link:https://circleci.com/app/home[CircleCI web app], select your organization.
-. Select **Projects** in the sidebar.
-. Find your project in the list, select the ellipsis (icon:ellipsis-h[]), select **Project Settings**.
-. Select **Deploys**.
-. Toggle the "Enable automatic deploy marker detection" option left. You will see a confirmation message in the bottom right hand corner of the app. To re-enable the feature, toggle the option to the right.
-
-=== Retention Policy
-
-Automatically detected deploys are retained for 30 days.
-
-=== Manual deploy marker setup
-
-If you would rather set up deploy markers yourself, see the xref:configure-deploy-markers#[Configure deploy markers] page.
+. Select **Deploys** in the sidebar.
+. Select the **Environments** tab.
+. Find your environment and select cog icon (icon:cog[]) to enter the environment integration settings page.
+. Select **Edit**.
+. Enter a new name and select btn:[Update].
 
 [#release-status]
 == Deploy status

jekyll/_cci2/introduction-to-the-circleci-web-app.adoc

@@ -247,7 +247,7 @@ Learn more and get started with self-hosted runners on the xref:runner-overview#
 
 **Self-Hosted Runners**: Accept the terms of use to enable self-hosted runners. Once accepted, you can visit the self-hosted runner section of the web application to create resource classes and set up runners.
 
-**Deploys**: Find links to set up deploy markers or deploy monitoring for your projects. Enable/disable autodetected deployments, which allows CircleCI to automatically detect deployments in your projects and create deploy markers for you.
+**Deploys**: Find links to set up deploy markers or deploy monitoring for your projects.
 
 **Integrations**: Set up integrations with self-hosted version control systems.