You will need roughly 2 minutes to read this article.
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.
To use your private Git server with Codeship, you will need a publicly reachable endpoint with ports 22 and 443 open to the internet.
We require port 22 to clone your repository to run your builds and port 443 for status and clone requests.
Note that Bitbucket Server uses port 7999 rather than port 22.
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.
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:
GitLab Community Edition
When you’re using a self-hosted git server, you will need to supply your username as well so that we can map up your builds with your Codeship account and show them on your personal dashboard. All users of self-hosted git servers will need to do this, for the personal dashboard to work, but are not required to supply access codes. If you don’t expect to be pushing code, and are mainly setting up Codeship for others, you can leave the username(s) blank.
Note: Users of cloud SCMs, who authenticate with oAuth, do not need to supply usernames as we get the username as part of the authentication workflow.
Note: Users who want to take advantage of the personal dashboard will need to supply their usernames, but don’t necessarily need to supply access tokens.
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.
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.
Do you think we need to improve this article? If so, please submit our feedback form to help us improve this article!