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

Ubuntu Focal

2 minute read

Ubuntu 20.04 LTS (Focal Fossa) On CloudBees CodeShip Basic

Ubuntu Focal build containers are now available for CloudBees CodeShip Basic. In general, the overall environment is setup and configured the same way you are familiar with. Most existing build commands should continue to work the same. The underlying OS version is Ubuntu 20.04 LTS (Focal Fossa).

Rollout Plan

On April 10, 2023 projects will automatically start running on Focal. This will be a progressive rollout over several weeks. If you would like your projects switched to Focal sooner, please let us know.

All projects need to be migrated to Focal by May 19, 2023. If you are unable to migrate by May 19th, your projects will be changed over for you which may result in failing builds.

Ubuntu Bionic reaches EOL at the end of May 2023.

If the build is running on Focal, step 6 of the build will say Preparing Ubuntu Focal Build Container.

Within that step, the logs also indicate the exact OS version:

Preparing...
Ubuntu 20.04.6 LTS

Key Changes

Common Issues

Many underlying package and dependency versions changed in Focal so it is possible you will encounter issues depending on your build configuration.

If you get unexpected errors the first step is to clear your project’s dependency cache. You can also add the cs clear-cache command to the start of the build to ensure the cache is not used while you are configuring the new environment.

If the build issues persist, then look at your build in a debug session which allows you to look closer and experiment with other build commands. If you did any special customizations to make your projects run in the Bionic environment, those customizations may need to either be updated for Focal, or in some cases you may no longer need them.

Keep in mind that you have sudo permissions in the build environment so you are free to use tools like apt-get to further customize the environment.

Finally, if you are using any CodeShip scripts they should work on Focal, but if you encounter any problems let us know. Also consider that with newer versions of many packages in Focal, you may not need a particular script any longer.

Opting Out

If you have a project that is failing on Focal and there is not a clear solution, you can opt that project out and stay on Bionic for now. Under Project Settings > General is a button to switch back to the old environment. All projects need to be migrated to Focal by May 19th.

Support

If the above steps do not help to get your projects running, reach out to us. We will help you work through any migration challenges.

Git LFS