spinnaker · agnihotrigaurav · Nov 11, 2022 · Nov 11, 2022 · Nov 11, 2022 · Nov 11, 2022
diff --git a/content/en/docs/guides/tutorials/codelabs/oci-source-to-prod/index.md b/content/en/docs/guides/tutorials/codelabs/oci-source-to-prod/index.md
@@ -7,7 +7,7 @@ description: >
 
 In this codelab, you will create a cohesive workflow which takes source code and builds, tests, and promotes it to production.
 
-Building the binary from the source code is done outside of Spinnaker, typically in a CI system such as Jenkins, Travis, or Wercker. Spinnaker is integrated with three CI systems.  Workflows can be triggered by jobs in these CI systems.  The easiest binary form for Spinnaker to produce machine image is debian or rpm packages.
+Building the binary from the source code is done outside of Spinnaker, typically in a CI system such as Jenkins or Travis. Spinnaker is integrated with three CI systems.  Workflows can be triggered by jobs in these CI systems.  The easiest binary form for Spinnaker to produce machine image is debian or rpm packages.
 
 To simplify this tutorial, we will use tomcat8 debian package as a starting point.  It is assumed your CI jobs build and publish packages such as tomcat8 and your CI jobs will be used to trigger the Spinnaker workflow.
 
@@ -214,7 +214,7 @@ Create a new pipeline by navigating to the PIPELINES tab and clicking the link *
 
 #### Configure the pipeline
 
-In reality, we would set up the pipeline with an automated trigger that will kick off the pipeline.  Assuming the package is built in CI (Jenkins/Travis/Wercker), in the Automated Triggers section of the pipelines form, you would add Jenkins/Travis/Wercker Trigger for your job so that every time these job completes the pipeline would start automatically.
+In reality, we would set up the pipeline with an automated trigger that will kick off the pipeline.  Assuming the package is built in CI (Jenkins/Travis), in the Automated Triggers section of the pipelines form, you would add Jenkins/Travis Trigger for your job so that every time these job completes the pipeline would start automatically.
 
 To simplify this tutorial, we will skip the trigger and use tomcat8 package.
 

diff --git a/content/en/docs/reference/halyard/commands.md b/content/en/docs/reference/halyard/commands.md
@@ -225,15 +225,6 @@ Published: 2020-04-30 21:10:29
 - [hal config ci travis master edit](#hal-config-ci-travis-master-edit)
 - [hal config ci travis master get](#hal-config-ci-travis-master-get)
 - [hal config ci travis master list](#hal-config-ci-travis-master-list)
-- [hal config ci wercker](#hal-config-ci-wercker)
-- [hal config ci wercker disable](#hal-config-ci-wercker-disable)
-- [hal config ci wercker enable](#hal-config-ci-wercker-enable)
-- [hal config ci wercker master](#hal-config-ci-wercker-master)
-- [hal config ci wercker master add](#hal-config-ci-wercker-master-add)
-- [hal config ci wercker master delete](#hal-config-ci-wercker-master-delete)
-- [hal config ci wercker master edit](#hal-config-ci-wercker-master-edit)
-- [hal config ci wercker master get](#hal-config-ci-wercker-master-get)
-- [hal config ci wercker master list](#hal-config-ci-wercker-master-list)
 - [hal config deploy](#hal-config-deploy)
 - [hal config deploy component-sizing](#hal-config-deploy-component-sizing)
 - [hal config deploy component-sizing clouddriver](#hal-config-deploy-component-sizing-clouddriver)
@@ -4193,7 +4184,6 @@ hal config ci [subcommands]
 - `gcb`: Manage and view Spinnaker configuration for Google Cloud Build
 - `jenkins`: Manage and view Spinnaker configuration for the jenkins ci
 - `travis`: Manage and view Spinnaker configuration for the travis ci
-- `wercker`: Manage and view Spinnaker configuration for the wercker ci
 
 ---
 
@@ -5146,197 +5136,6 @@ hal config ci travis master list [parameters]
 
 ---
 
-## hal config ci wercker
-
-Manage and view Spinnaker configuration for the wercker ci
-
-#### Usage
-
-```
-hal config ci wercker [parameters] [subcommands]
-```
-
-#### Parameters
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
-#### Subcommands
-
-- `disable`: Set the wercker ci as disabled
-- `enable`: Set the wercker ci as enabled
-- `master`: Manage and view Spinnaker configuration for the wercker Continuous Integration services's master
-
----
-
-## hal config ci wercker disable
-
-Set the wercker ci as disabled
-
-#### Usage
-
-```
-hal config ci wercker disable [parameters]
-```
-
-#### Parameters
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
----
-
-## hal config ci wercker enable
-
-Set the wercker ci as enabled
-
-#### Usage
-
-```
-hal config ci wercker enable [parameters]
-```
-
-#### Parameters
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
----
-
-## hal config ci wercker master
-
-Manage and view Spinnaker configuration for the wercker Continuous Integration services's master
-
-#### Usage
-
-```
-hal config ci wercker master MASTER [parameters] [subcommands]
-```
-
-#### Parameters
-
-`MASTER`: The name of the master to operate on.
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
-#### Subcommands
-
-- `add`: Add a master for the wercker Continuous Integration service.
-- `delete`: Delete a specific wercker master by name.
-- `edit`: Edit a master for the wercker Continuous Integration service.
-- `get`: Get the specified master details for wercker.
-- `list`: List the master names for wercker.
-
----
-
-## hal config ci wercker master add
-
-Add a master for the wercker Continuous Integration service.
-
-#### Usage
-
-```
-hal config ci wercker master add MASTER [parameters]
-```
-
-#### Parameters
-
-`MASTER`: The name of the master to operate on.
-
-- `--address`: (_Required_) The address your Wercker master is reachable at.
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
-- `--token`: (_Sensitive data_ - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
-- `--user`: The username of the Wercker user to authenticate as.
-- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
-
----
-
-## hal config ci wercker master delete
-
-Delete a specific wercker master by name.
-
-#### Usage
-
-```
-hal config ci wercker master delete MASTER [parameters]
-```
-
-#### Parameters
-
-`MASTER`: The name of the master to operate on.
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
----
-
-## hal config ci wercker master edit
-
-Edit a master for the wercker Continuous Integration service.
-
-#### Usage
-
-```
-hal config ci wercker master edit MASTER [parameters]
-```
-
-#### Parameters
-
-`MASTER`: The name of the master to operate on.
-
-- `--add-read-permission`: Add this permission to the list of read permissions.
-- `--add-write-permission`: Add this permission to the list of write permissions.
-- `--address`: The address your Wercker master is reachable at.
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-- `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
-- `--remove-read-permission`: Remove this permission from the list of read permissions.
-- `--remove-write-permission`: Remove this permission from the list of write permissions.
-- `--token`: (_Sensitive data_ - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
-- `--user`: The username of the Wercker user to authenticate as.
-- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
-
----
-
-## hal config ci wercker master get
-
-Get the specified master details for wercker.
-
-#### Usage
-
-```
-hal config ci wercker master get MASTER [parameters]
-```
-
-#### Parameters
-
-`MASTER`: The name of the master to operate on.
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
----
-
-## hal config ci wercker master list
-
-List the master names for wercker.
-
-#### Usage
-
-```
-hal config ci wercker master list [parameters]
-```
-
-#### Parameters
-
-- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
-- `--no-validate`: (_Default_: `false`) Skip validation.
-
----
-
 ## hal config deploy
 
 Display the configured Spinnaker deployment.

diff --git a/content/en/docs/reference/pipeline/stages/_index.md b/content/en/docs/reference/pipeline/stages/_index.md
@@ -248,13 +248,6 @@ dropdown menu.
 You can [add more certification authorities](/docs/guides/operator/webhook-custom-trust-store/)
 to trust when making webhook calls over HTTPS.
 
-### Wercker
-Run the specified Wercker pipeline. You must [set up Wercker](/docs/setup/other_config/ci/wercker/)
-in order to use this stage. Once Wercker has been configured, your Wercker
-masters and the applications and pipelines available for your master's
-credentials will be shown in the drop-down menus. When a Wercker pipeline stage
-runs, a link to the Wercker run will be available, and the status of
-the Wercker run will be reported in Spinnaker.
 
 ## App Engine
 

diff --git a/content/en/docs/setup/other_config/ci/_index.md b/content/en/docs/setup/other_config/ci/_index.md
@@ -26,6 +26,5 @@ These are the CI systems currently supported by Spinnaker:
 * [Google Cloud Build](/docs/setup/other_config/ci/gcb/)
 * [Jenkins](/docs/setup/other_config/ci/jenkins/)
 * [Travis CI](/docs/setup/other_config/ci/travis/)
-* [Wercker](/docs/setup/other_config/ci/wercker/)
 
 See also [hal config ci](/docs/reference/halyard/commands/#hal-config-ci).
diff --git a/content/en/docs/setup/other_config/ci/wercker.md b/content/en/docs/setup/other_config/ci/wercker.md