CodeShip Status

Resolved The CodeShip website is not reachable

We are currently investigating this issue.

Resolved CodeShip application access

We are working to resolve issues preventing the CodeShip application from resolving. Service should be restored shortly.

Resolved Performance issues processing builds and reporting via website

We are investigating a build scheduling performance issue. There will be a short interruption to build process while we complete a system upgrade to alleviate stress on the system.

Resolved Pro build issues

We are hearing reports that some Pro builds are performing abnormally. Please contact us ([email protected]) with more information if you are seeing any odd behavior, and we will continue investigating.

Resolved CodeShip Pro maintenance

CodeShip Pro is under maintenance for about 60 minutes. During this time builds will be disrupted.

Resolved Basic builds delayed

We are currently investigating this issue.

Resolved CodeShip Basic builds not completing

We are investigating an issue with CodeShip Basic builds not completing execution properly.

Resolved CodeShip builds not running

We are currently investigating this issue.

Resolved System upgrades - Application Servers

We are performing upgrades to our application servers (component updates). We do not expect any disruption of service, but builds may be temporarily delayed as we update the platform.

Resolved [Security] Critical Security Notification - CodeShip Users

On Wednesday, September 16, 2020, CloudBees was notified by GitHub of suspicious activities targeting certain CodeShip accounts connected to GitHub via the CodeShip GitHub app and now deprecated CodeShip OAuth tokens. If your GitHub credentials are impacted, you already received or will shortly receive a notification from GitHub informing you of this incident. The activities point to tokens being used to access the “/user/repos” GitHub API endpoint (https://docs.github.com/en/[email protected]/rest/reference/repos#list-repositories-for-the-authenticated-user), which is used to list users’ GitHub repositories, including private repositories. It is possible your repositories were cloned, so please contact GitHub support as soon as possible. Because the suspicious activities involve user tokens, as a first step in response we revoked all GitHub related tokens and SSH keys to keep all accounts protected. You need to reauthenticate CodeShip with GitHub immediately to avoid a service impact. *Action Required* - If you use GitHub to sign in to CodeShip, sign out of all CodeShip sessions and sign back in. - If you have GitHub projects setup on CodeShip, first remove and reinstall the CodeShip GitHub app: https://documentation.codeship.com/general/projects/builds-are-not-triggered/#github - Next, generate a new SSH key for each CodeShip project. This will enable CodeShip to clone the repository for builds again: https://documentation.codeship.com/general/projects/project-ssh-key/ We are continuing to investigate the underlying issue and will update our blog to provide more information as soon as we better understand any additional implications and potential root causes. Thank you. The CloudBees Team