This article is about General Codeship Configuration.

Self-hosted SCM

You'll need about one minute to read this article.

Beta Access

Codeship supports self-hosted Git repositories for the GitHub Enterprise, GitLab Community Edition, GitLab Enterprise Edition and Bitbucket Server products.

This is a beta feature and you will need to contact us and request access.

Exposing Ports

To use your private Git server with Codeship, you will need a publicly reachable endpoint with ports 22 and 433 open to the internet.

We require port 22 to clone your repository to run your builds and port 433 for status and clone requests.

Note that Bitbucket Server uses port 7999 rather than port 22.

Personal Access Tokens

To connect to your self-hosted Git instance, you will need to retrieve your personal access token and add it to your Connected Services screen.

On Codeship, you can find your Connected Services screen by navigating to once you’ve logged in.

To fetch your token, follow these instructions:

Note that Codeship requires Bitbucket Server 5.5 due to prior versions not providing personal access tokens.

IP Whitelisting

We are currently planning a beta to make available a limited number of IPs for whitelisting and network access purposes.

For now, the above ports need to be made available to the public internet but please contact us if you are interested in our upcoming IP whitelisting feature.

SCM Feature Requests

We are continually evaluating our SCM integration support. If there is something you would like to see, please get in touch and let us know more details about your SCM needs.


To read more about our security setup, please review our security documentation or ask us a question.