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

CodeShip Retirement FAQ

1 minute read

This FAQ addresses common questions to support a successful transition. For additional help, contact Cloudbees Support.

🔄 Why is CodeShip being discontinued?

CodeShip is being retired to make way for CloudBees Unify, a more advanced, scalable, and flexible cloud-native DevOps solution. CloudBees Unify enhances the development lifecycle with a self-service model, a Tekton-based CI/CD engine, and seamless integration with modern DevOps tools. It also reduces developer cognitive load while offering centralized security, built-in compliance, and automated DevSecOps capabilities.

🚀 What is CloudBees Unify, and how does it differ from CodeShip?

CloudBees Unify is a comprehensive DevOps solution that simplifies cloud-native development and deployment. It includes:

  • Centralized security

  • Advanced analytics

  • Feature management

  • Release orchestration

  • Extensive integration capabilities

These features go beyond what CodeShip offers.

📅 What is the timeline for the transition?

CodeShip will be fully decommissioned on January 31, 2026. Complete all migrations before this date to avoid service disruption.

🛠️ Is there a migration guide?

Yes, CloudBees provides a step-by-step guide.

🔒 What happens to CodeShip accounts after migration?

Once migration is complete and a CloudBees Unify plan is selected, the CodeShip account will be deactivated. For billing or deactivation help, contact CloudBees Support.

📚 Is documentation available for CloudBees Unify?

Yes. Documentation is available to help teams ramp up quickly and effectively:

💲 Are there additional costs?

CloudBees Unify offers multiple pricing tiers. Refer to the Pricing page for full details.

As a benefit, existing CodeShip customers who migrate can maintain current pricing by contacting CloudBees Support after migration to enroll in the appropriate plan.

Customer Success Stories