Getting started
IntroductionInstalled packagesEnvironment variablesDebugging buildsCachingParallel testingDeployment pipelinesRunning commands as rootIgnoring commandsRun a command in case of an errorSetting timezoneAccess to other repositoriesUsing scriptsGit LFSUbuntu 20.04 Focal
IntroductionFTP/SSH/SFTP/RSYNCCustom scriptHerokuHeroku MigrationAWS Elastic BeanstalkAWS CodeDeployAWS LambdaAWS S3Google App EngineAWS CLIgcloud CLIAzure CLIDigital OceanEngine YardCapistranoGit PushCloudFoundryCloud66anynines
IntroductionBrowser testingBackground commandsGit submodulesCustom DNSArtifacts
IntroductionCassandraCouchDBDynamoDBMongoDBMySQLPostgreSQLSQLite
IntroductionDartElixirGoJava and JVMMeteorNode.jsPHPPythonRubyRust
IntroductionBeanstalkdRabbitMQRedis
IntroductionElasticsearchMemcachedSphinx
IntroductionUsing AnchoreUsing CodeShip APIUsing AppranixUsing AssertibleUsing AtatusUsing CodacyUsing CodeclimateUsing CodecovUsing CoverallsCustom integrationsUsing DepfuUsing FirebaseUsing Ghost InspectorUsing GosecUsing HoneycombUsing OpsGenieUsing PagerDutyUsing PercyUsing PulumiUsing RancherUsing RaygunUsing RedLine13Using RollbarUsing RunscopeUsing SnykUsing Testable
IntroductionCloudBees CodeShip Pro introduction guideCloudBees CodeShip Pro introduction guide 2CloudBees CodeShip Pro introduction guide 3CloudBees CodeShip Pro introduction guide 4CloudBees CodeShip Pro introduction guide 5
Migrating to CloudBees CodeShip Pro
Docker for CI/CD
Getting started with CloudBees CodeShip Pro overview and resources
IntroductionServices configSteps configEnvironment variablesImage registriesImage cachingBuild argumentsVolumesHandling secretsMultiple reposServices and databasesSetting an SSH private keyPreinstalled images
IntroductionInstallationUsing the Jet CLIjet cleanupjet decryptjet encryptjet generatejet loadjet runjet stepsjet updatejet validatejet version
IntroductionAWSAWS S3AWS EBAWS ECSAWS EKSAWS CodeDeployAzure Container ServiceHerokuGoogle CloudGoogle App EngineGoogle Cloud FunctionsGoogle Container EngineGoogle Compute EngineKubernetesTerraformDeploy Via SSHDocker SwarmIBM Cloud FoundryIBM Cloud Container Service
IntroductionBrowser testingParallel testing
IntroductionElixirGoJava and JVMNode.jsPHPPythonRuby
IntroductionCaching multi-stage DockerfileContainer is slow to exitDiffering results with Jet CLIDocker Hub rate limitingManaging multiple environments for a serviceReducing log output from dependent containersStep log not appearingUsing env vars in command steps
IntroductionUsing AnchoreUsing CodeShip APIUsing AppranixUsing AssertibleUsing AtatusUsing CodacyUsing CodeclimateUsing CodecovUsing CoverallsCustom integrationsUsing DepfuUsing FirebaseUsing Ghost InspectorUsing GosecUsing HoneycombUsing OpsGenieUsing PagerDutyUsing PercyUsing PulumiUsing RancherUsing RaygunUsing RedLine13Using RollbarUsing RunscopeUsing SnykUsing Testable

Troubleshooting Issues With Builds Not Starting

2 minute read
On this page

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.

Webhooks

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.

GitHub

Make sure the CodeShip GitHub app has been installed in 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.

Github Apps Configuration

GitLab

Make sure a webhook for CodeShip is added under the Webhooks section in the settings of your repository. The Gitlab documentation has more information.

Bitbucket

Make sure a webhook for CodeShip is added under the Webhooks section in the settings of your repository. Please also check the UUID in the hook URL matches the UUID from your project. The hook URL itself should match the following pattern.

https://lighthouse.codeship.io/bitbucket_v2/YOUR_PROJECT_UUID

BitBucket Webhooks Configuration

Verifying Branches Aren’t Excluded

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.

Exclude branches from running builds

Git remote push