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

Git submodules

1 minute read

If your repository includes a .gitmodules file, CodeShip will automatically initialize and update the configured submodules. The following command is run after cloning your repository to do this.

git submodule update --recursive --init
▼
Right now there is no way to skip this command, but let us know if that creates a problem for your build.

Submodule Permissions

Submodules that are hosted as public repositories should just work, but let us know if you see any issues.

If your submodule is a private repository, you need to make sure CodeShip can clone the repository.

  1. Make sure the project’s public SSH key (from the General settings page) has access to the submodule repository. See how to provide access to other repositories if you’re not sure how to achieve this.

  2. Make sure the submodule is referenced via an SSH-based URL (for example git@github.com:codeship/documentation.git). If you reference the submodule via an HTTPS based URL (for example https://github.com/codeship/documentation.git), the git client will ask for authentication credentials during the build and run into a timeout (as you can’t provide them).

See the git documentation on Git Submodules for more information on working with submodules.

Typical Error Messages

See how to provide access to other repositories if you see an error like these.

remote: Repository not found
fatal: Could not read from remote repository
Permission denied (publickey).
Please make sure you have the correct access rights
and the repository exists.
Clone of 'git@bitbucket.com:username/reponame.git' into submodule path 'path' failed
Background commands
Custom DNS