Getting Started With Projects

The first thing you need to select, when creating a new project, is where your code is located. You can use GitHub, Bitbucket, or GitLab in either their cloud version or as a self-hosted git server.

If you select to use a cloud-based GitHub repository, you will be asked to first select the GitHub organization that owns the repository, and then to select the repository itself. If you don’t see your organization or repository in either of the dropdown boxes, you will likely need to first install the CodeShip GitHub app and/or allow the app access to the repository you’re trying to setup a project for.

If you select to use one of the other options, you will need to first get a link to the repository from your git server

To get started with a CodeShip project, you will want to have a few resources available:

You need to have project ownership for deleting a project. Once you click the delete button, you will have to confirm the deletion once more.

A project can be deleted by going to Project Settings on the project builds view, selecting the General tab and click the Delete this project button

All your builds will be deleted as well. Make sure that you really don’t need this project anymore as it cannot be recovered once deleted.

Right now it is not possible to rename a project. You will need to remove and re-add the project if a repo’s name changed and you want to reflect this in CodeShip.

If you need to create a large number of projects, or maybe just create similar projects on a regular basis, you can use the API to do the heavy lifting and just have a template on your side that forms the basis for all new projects. To learn more, head over to the API Documentation page.

You can transfer your project to another account by navigating to:

Project Settings > General

A user with appropriate permission for the target account needs to confirm the transfer if you do not have project creation rights in the target account. When confirming the transfer, the user can choose which of the current team members to keep and which to remove.

If you want to bulk transfer projects, please reach out to our support via app.codeship.com.

We don’t have a feature to limit which branches can be built.

We build your project on every push (that is, we run your setup and test commands) to let you know as soon as possible if something is broken. We will only ever run a deployment for the specific branch it is configured on and only after all setup and test commands executed successfully. Before deployment, every push to your repository should be tested.

If you wish to skip a build, please refer to the article about skipping builds.

CodeShip does not support testing pull requests from forked repositories. You need to configure the forked repository separately on CodeShip or push the branch to the already configured repository instead.

To make it easier to navigate through your CodeShip projects, we’ve provided several keyboard shortcuts for quickly jumping through the interface:

Once you’ve created your project, you can invite colleagues members to give them access.

Under Project Settings > Team members, simply add their email address to send them an invite.

CodeShip is hosted on AWS EC2 in the us-east-1 region. Because of this, CodeShip services do not have static IP addresses by default. There are several different options for allowing CodeShip to pass through your firewall.

If your build can’t locate a configuration file which you ignored in your repository, via .gitignore, create a your_config.yml.example with data that works for your tests and add it to your repository. Then add the following command to your setup commands so the YAML file is properly set up.

You should also check that you are not coming from a case-insensitive operating system where you may not have noticed that the file name is different, i.e. File.yml compared to file.yml.