Security specifications

For every project you add to CodeShip we create a SSH key that is itself encrypted strongly and only decrypted shortly before being used in the build virtual machine. For every build we start a new and clean virtual machine. All changes you make (including file system changes) are stored in a ramdisk which is removed as soon as your build finishes (tests and deployment). None of your data is ever stored on any hard drive on our build servers.

All communication between your browser and our website is SSL encrypted, as is all communication to our Openredis queue. All communication to the build virtual machines is done over SSH.

On CloudBees CodeShip Basic, with permission, our support team can open a SSH debug session which allows us to see your source code.

On CloudBees CodeShip Pro, we have no direct access to your source code but our support team can see your builds and build logs, as well as account information.

To run your tests, we need to check out your code from your source code provider. We support GitHub, GitLab, and Bitbucket. You can sign up for CodeShip via email as well but as soon as you connect a repository with your CodeShip account you are telling your source code provider that you allow us to check out your private repositories.

You can revoke permission in your source code provider settings and by removing CodeShip’s deploy keys and service hooks from your projects’ configuration pages.

If you need to access resources behind a custom firewall from CodeShip, e.g. pulling code from a self-hosted git server or perhaps deploying build artifacts to an internal environment, you can enable the static IP addresses feature and only open the necessary ports for those IPs in your firewall. See Static IP Addresses documentation for more details.

Yes, we comply with GDPR as a controller. See more on the GDPR page.

Our whole infrastructure is based on Amazon EC2 or services built on top of it. EC2 is one of the most trusted, tried and tested hosting services out there. The services we use are:

Additionally for monitoring the platform, handling payments, and potentially collecting metrics we use:

Note: Although we do have access to your source code, as outlined in our Terms of Service, we only access it for a build or support request. We do not have any way to access your source code repository outside of our build environment.

CodeShip never takes ownership of your code or files. All builds run on containers or machines that are shut down at the end of your build, with your cloned repository and generated assets never persisted between builds.

The one exception is with opt-in caching. On CodeShip Basic we will save your dependencies automatically (but not your code) and on CodeShip Pro we will save your images if you explicitly tell us to in your project configuration.

In the case of CloudBees CodeShip Pro’s image caching, we save each project’s images in AWS with security credentials specific to that project.

Yes, from time to time CodeShip will hire external parties to examine and audit current security practices.

For various roles, CodeShip will hire part-time workers or third-party contractors. All employees - full-time, part-time or external - are given appropriately limited resource access and security requirements.

We have a more detailed security checklist available on request. Get in touch if you need more information.

CodeShip uses a variety of third-party JavaScript embeds to perform a variety of user and business functions.

Note that third-party tracking is enabled on all application pages.

If you have not allowed us to capture data on how you use CodeShip (part of GDPR) we will not embed Segment.

All JavaScript code running in the browser, including code from the trusted third-parties listed above, has access to any information that is transmitted to the browser at run time. No sensitive information is sent to third-party tracking functions. Code running the browser does not have restricted API access to any sensitive information that is not displayed in the browser.

If you have further questions or want to report a vulnerability please contact security@cloudbees.com.