You will need about one minute to read this article.
If your builds are not getting triggered on Codeship, it could be that we are experiencing a service interruption. Be sure to check our status page to monitor any potential issues. You can also follow the @CodeshipStatus account on Twitter.
Builds on Codeship are triggered via a webhook from your source control repository. This webhook is added to your repository when you connect the project to Codeship, but sometimes those settings get out of sync.
Depending on your SCM, the process to fix this is a bit different.
Make sure the CodeShip Github App has been installed on your Github organization that owns the repository for your project. You also need to ensure that the CodeShip Github App has been allowed to access the repository. To install or update your CodeShip Github App, go to your Github Organization Settings and select the Installed Github Apps menu. If the CodeShip Github App is not installed it will not show up; if it is installed click the Configure button to update the list of allowed repositories.
Make sure a webhook for Codeship is added under the Webhooks section in the settings of your repository. The Gitlab documentation has more information.
Make sure a webhook for Codeship is added under the Webhooks section in the settings of your repository. Please also check the the UUID in the hook URL matches the UUID from your project. The hook URL itself should match the following pattern.
Because you can use the Branches tab in your Project Settings to exclude certain branches from running builds, or to only run builds on certain branches, you should verify that your branches are not excluded if you are seeing builds fail to trigger.
Contact our support team or post on Stack Overflow using the tag
#codeship. Did you check the status page and changelog?
There are also several code examples and sample projects available for you to get started with.