How to delete your Codeship by CloudBees account

About deleting your Codeship by CloudBees account

Codeship by CloudBees is a continuous integration and continuous delivery (CI/CD) platform designed to help development teams automate their testing and deployment workflows. It integrates directly with source control providers like GitHub, Bitbucket, and GitLab to build, test, and deploy applications in the cloud. Because it handles the backbone of software delivery, it interacts with proprietary source code, environment variables, API keys, and deployment credentials for your production infrastructure.

Users often choose to delete their Codeship by CloudBees account for several specific reasons related to the sensitivity of their DevOps ecosystem:

• Migrating to self-hosted CI/CD solutions like Jenkins, GitHub Actions, or GitLab CI to regain full control over infrastructure.
• The decommissioning of legacy projects that no longer require automated cloud builds.
• Reducing the attack surface by minimizing the number of external platforms that hold read/write access to internal code repositories.
• Dissatisfaction with service updates or changes to the CloudBees ecosystem architecture.

What happens to your data

When you request the deletion of your Codeship account, CloudBees generally initiates a process to scrub user-specific identifiers and configuration data from their active databases. However, because Codeship acts as an automation bridge, the scope of what is removed is distinct:

• Collected Data Types: Your Codeship account retains repository connection metadata, build logs, environment variable values, notification settings, and user authentication tokens.
• Retention and Removal: While active build logs and project configurations are slated for deletion, CloudBees may retain certain data for billing, legal compliance, or aggregate service performance analysis.
• Backup Cycles: Your data may persist in off-site backups or immutable logs for a set period before being overwritten according to CloudBees' internal data lifecycle policies.

Privacy considerations

Using a hosted CI/CD service like Codeship introduces specific privacy considerations regarding the management of secrets and code access. Because the platform requires OAuth tokens to interface with your repositories, the privacy of your codebase is intrinsically tied to the security of your Codeship account.

To better protect your privacy when using or departing from Codeship:

• Revoke OAuth access: Before deleting your account, navigate to your GitHub or Bitbucket settings and explicitly revoke the OAuth application permissions previously granted to Codeship.
• Rotate your secrets: If you stored production API keys or database credentials as environment variables in Codeship, rotate them immediately after deleting your account.
• Audit webhook activity: Ensure that no lingering webhooks exist in your source control pointing back to the decommissioned Codeship service.

Frequently Asked Questions

Can I delete my Codeship account through the settings dashboard?

No, there is currently no self-service 'delete account' button within the Codeship dashboard. You must contact their support team directly to initiate the removal.

Will deleting my account automatically revoke my GitHub/GitLab integration?

It is highly recommended that you manually revoke the OAuth access in your source control provider settings to ensure that the bridge between your repository and Codeship is fully severed.

Does deleting my account remove my build logs?

Yes, account deletion requests generally include the removal of your project-specific build history and logs from the Codeship interface, though historical data might exist in encrypted archives for a limited time.

Are my environment variables permanently erased upon account deletion?

Yes, once the account is processed for deletion, the environment variables used for your builds are removed from the active production environment and are no longer accessible.

Can I reactivate my account after requesting deletion?

Usually, deletion requests are treated as permanent. If you believe you may need your build history in the future, ensure you export your build logs and configuration files before requesting the account closure.