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

Properties

1 minute read

Use properties to define variables and secrets at the organization or sub-organization level. A property is a key-value pair used to configure various platform elements such as actions, environments, or integrations.

Typical uses include:

  • Credentials (e.g., usernames, passwords, personal access tokens)

  • SCM metadata (e.g., repository URLs, commit hashes)

  • General configuration (e.g., API endpoints, deployment regions, artifact paths)

  • Supported data types: String, Number, Boolean.

Organization-Level Properties

  • Scope: Available to all applications, workflows, and sub-organizations.

  • Purpose: Define global configurations or shared credentials.

  • Example: ARTIFACT_REPO_URL, LOG_SERVICE_API_KEY

  • Inheritance: Sub-organizations and workflows inherit these properties by default.

Sub-Organization-Level Properties

  • Scope: Restricted to the specific sub-organization.

  • Purpose: Support department-specific or project-specific settings.

  • Example: FINANCE_TEAM_API_ENDPOINT, PROJECT_X_JIRA_TOKEN

  • Overrides: Sub-organization-level definitions take precedence over Organization-level ones with the same name.

  • For more information, refer to Properties.

Environment Variables