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

Using sudo or root

2 minute read

Sudo and root on CloudBees CodeShip Basic

Although CloudBees CodeShip Basic already has a long list of packages installed, you can install most packages yourself if you find that something is missing. CloudBees CodeShip Basic supports running commands as sudo giving you root-level access; with a few caveats.

What can you do?

With the sudo access, you can run apt-get update and apt-get install <package> to install packages, even if they would normally require root-level access.

You can also start new services (custom or standard), assuming they don’t try to do any of the things mentioned below.

Note: When you are looking for packages to install, look for those that work on Ubuntu 20.04 (Focal Fossa) as that is the underlying Linux we use for the build machines.

What can’t you do?

Although you get sudo/root-level access, there are still things you can’t do as CloudBees CodeShip Basic is still a shared platform:

  • Don’t try and change system level resources

    • Resource limits (prlimit/ulimit/etc.)

    • Networking resources or settings (incl. adding IP addresses)

    • Loading kernel modules

    • Anything that relies on apparmor/selinux access

  • Don’t attempt to run any type of virtualization (virtual machine, docker, LXC, or other container-based tech).

  • Don’t expect any UI/Desktop-related stuff to work either. Headless browser testing is fine, but don’t install an x-server and run gnome.

What To Do If Things Fail?

With so many pre-installed packages, and the amount of packages that could potentially be installed, it’s not unthinkable that what you’re trying to do might not work.

Main thing to check is to make sure that whatever you’re trying to install or start doesn’t try to change resources (or anything else in the list above).

It is also possible (esp. for language versions) that you can install it differently, without having to manually install the package. An example could be installing a different version of Ruby using rvm. If it’s not a language, double check the list of installed packages

And if it’s still failing, contact us so we can help you figure out what’s going on.

Deployment pipelines
Ignoring commands