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

Jet load

1 minute read

Description

Pull an image or build a docker service

Usage

jet load service [flags]

Flags

Name, shorthand

Default

Description

--ci-branch

The name of the branch being built

--debug

Turn debug output on

--dir

Current Directory

The directory to use

--dockercfg-service

The name of the service with which the dockercfg should be generated

--encrypted-dockercfg-path

The path to the encrypted dockercfg file to be used

--key-path string

codeship.aes

The key path for encrypting secure environment variables.

--no-remove

Do not remove any containers that are run, overrides all other settings

--pull-if-present

false

Pull images that are already present

--services-path string

codeship-services.yml

The relative services path

Extended Description

The jet load command allows you to build a service without executing anything. This can be helpful for debugging, e.g. if one particular service fails to load correctly you can isolate the issue by loading only that service. You can load a service defined in the codeship-services.yml file.

Examples

$ jet load web

(step: web-36a86f22)
(image: registry.heroku.com/todos-js/web) (service: web) Step 1/7 : FROM node:8.6.0-alpine
(image: registry.heroku.com/todos-js/web) (service: web)  ---> b7e15c83cdaf
...
(step: web-36a86f22) success ✔
▼
jet generate
jet run