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

SCM Support on CloudBees CodeShip

2 minute read

CloudBees CodeShip supports Git repositories hosted directly on GitHub, Bitbucket and GitLab. There is support for on-premise versions of these SCM systems as well.

Integration between a repository and any forked repositories is not currently supported for any SCM. You can setup forked repositories as separate projects on CodeShip, but any builds for the forked repository will not link back to the parent repository.

Get started by creating a project on CodeShip. If you are having trouble getting your SCM connected to CodeShip, check that the correct permissions are set.

GitHub

Bitbucket

GitLab

Self-hosted Git Servers

There is support of GitHub Enterprise, GitLab Community Edition, GitLab Enterprise Edition and Bitbucket Server products.

You can read the self-hosted Git documentation to learn more.

If you use self-hosted git servers, we have a static IP addresses feature, which allows you to provide access to your git server, from just eight specific IP addresses. See Static IP Addresses documentation for more details.

Managing Your Git Server Connections

If you want to see which services you’re connected to, or perhaps ensure your username is registered so your builds show up on the personal dashboard, you can go to your Connected Services page. This allows you to add more connections or update/disable your existing connections.

Note: Before disconnecting a service, you should check to see if it’s being used by a project to communicate with your git server. The account used to connect to the git server is shown on the project’s General settings (Project → Project Settings → General).

Getting started with CI & CD
Configuring GitHub