This article is about General Codeship Configuration.

Self-hosted SCM

You'll need roughly 2 minutes to read this article.

Enterprise Support

Codeship supports self-hosted Git repositories for the GitHub Enterprise, GitLab Community Edition, GitLab Enterprise Edition and Bitbucket Server products - in addition to our standard cloud SCM support.

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 page.

To fetch your token, follow these instructions:

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

Token Access Scopes

In order for Codeship to be allowed to setup the necessary hooks etc. the personal access tokens need to have the correct set of scopes. Below you’ll find the necessary setting for each of the three self-hosted Git servers:

GitHub Enterprise

GitHub Enterprise Access Scopes

GitLab Community Edition

GitLab Community Edition Access Scopes

Bitbucket Server

Bitbucket Server Access Scopes

IP Whitelisting

We have an IP Whitelisting option, which allows you to provide access to your git server, from just eight specific IP addresses. See IP Whitelisting documentation for more details.

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.