• Documentation
    Software Delivery Automation
    CloudBees CICloudBees CD
    Other CloudBees Products
    CloudBees Build AccelerationCloudBees CodeShipCloudBees Jenkins PlatformCloudBees Jenkins Distribution
    Software Delivery Management
    CloudBees Engineering EfficiencyCloudBees Feature ManagementCloudBees Value Stream Management
  • Plugins
    CloudBees CI Plugins(CloudBees Core)CloudBees CD Plugins(CloudBees Flow)
  • Lexicon
  • Search
  • Support
  • New to CloudBees or returning.
    Sign in / Sign up

SELECT PRODUCT

CloudBees CICloudBees CDCloudBees Engineering EfficiencyCloudBees Feature ManagementCloudBees Build AccelerationCloudBees Value Stream ManagementCloudBees CodeShipCloudBees Jenkins PlatformCloudBees Jenkins DistributionCloudBees Jenkins EnterpriseCloudBees LexiconLegal and policiesDocSite usage
DocumentationChangelog
Introduction
Getting started
Builds and configuration
Continuous deployment
Continuous integration
Databases
Languages and frameworks
Queues
Services
About
Account
Integrations
Projects
Getting started
Migrating To Pro
Docker For CI/CD
Getting started with CloudBees CodeShip Pro overview and resources
Builds and configuration
Jet CLI
InstallationUsing the Jet CLIjet cleanupjet decryptjet encryptjet generatejet loadjet runjet stepsjet updatejet validatejet version
Languages and frameworks
Continuous integration
Continuous deployment
Common issues
Integrations
About
Account
Projects

Jet generate

On this page
  • Description
  • Usage
  • Extended description

Description

Generate an AES key for encrypting files.

Usage

jet generate [flags]

Extended description

The AES key created using jet generate will is not available in CodeShip during the remote execution. You can use this command to create local keys for initial testing. Any files that should be decrypted remotely would need to use the key found in your Project Settings during the execution of jet encrypt.

jet encrypt
jet load
© CloudBees, Inc. 2010 - 2020
Privacy Policy|Legal Notices|Security