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 Brakeman ProUsing 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 Brakeman ProUsing CodacyUsing CodeclimateUsing CodecovUsing CoverallsCustom integrationsUsing DepfuUsing FirebaseUsing Ghost InspectorUsing GosecUsing HoneycombUsing OpsGenieUsing PagerDutyUsing PercyUsing PulumiUsing RancherUsing RaygunUsing RedLine13Using RollbarUsing RunscopeUsing SnykUsing Testable

Using the Jet CLI

2 minute read

If you are unfamiliar with CloudBees CodeShip Pro, we recommend our getting started guide or the features overview page. Note that if you are using CloudBees CodeShip Basic, you will not be able to use the local CLI.

Using The Jet CLI

To list available commands, run jet with no parameters, jet -h or jet --help:

$ jet

Usage:
  jet [command]

Available Commands:
  cleanup     Remove docker resources left behind by jet
  decrypt     Decrypt a file using an AES key
  encrypt     Encrypt a file using an AES key
  generate    Generate an AES key for encrypting files
  help        Help about any command
  load        Pull or build service images
  run         Run a command inside a service container
  steps       Run steps
  update      Download and install the latest version of Jet
  validate    Validate codeship-services.yml and codeship-steps.yml files
  version     Display the jet version

Flags:
  -h, --help   help for jet

Use "jet [command] --help" for more information about a command.

Troubleshooting With Jet

Because the Jet CLI accurately reproduces your CI/CD build pipeline locally, you can use it to quickly solve difficult problems.

For instance, if a test or command fails on a build in CodeShip, you can try to reproduce the error with jet steps. When you want to test a change, jet steps will let you verify the change is working prior to committing so that you don’t have to wait for the full build to run remotely to get feedback.

We recommend that developers using CodeShip make use of the Jet CLI to improve productivity and solve build-related issues.

The results of a jet steps run can differ from the corresponding CloudBees CodeShip Pro build. We’ve listed a number of reasons for why that may be the case.

Examples

Display help text

To list the help for any command, execute the command followed by the -h or --help flag.

$ jet steps -h
Run steps

Usage:
  jet steps [flags]

Flags:
      --ci-branch string                  The name of the branch being built
      --ci-build-id string                The id of the build being run
...

Option types

Multi

Some flags like -e=[ ] may be used multiple times in a single command line, for example:

$ jet steps -e foo=bar -e baz=qux

String and Integers

Some flags require a string like --ci-branch and can only be specified once.

$ jet steps --ci-branch master
Installation
jet cleanup