Blossom Docs
Blossom

Reference

blossom job:run:create

cli reference 3 min read

Run a saved Job or an ad hoc Environment command

Usage

blossom job:run:create [--job JOB] [--environment ENVIRONMENT] [--command COMMAND] [--data DATA] [--follow] [--timestamps]

Flags

Flag Description
--job Saved Job id; alternative to –environment
--environment Environment id for an ad hoc command; alternative to –job
--command Ad hoc command using default resources; alternative to –data
--data, -d Ad hoc Job Run YAML/JSON data, file, or URL; alternative to –command
--follow, -f Follow this execution to its terminal result
--timestamps Show log timestamps. Default: true.

Create a Job Run using its Environment’s current successful Release and variables. Choose exactly one target: a saved Job or an Environment for an ad hoc command. Neither path creates a Build or Deploy.

blossom job:run:create --job job-100 --follow
blossom job:run:create --environment environment-100 --command "bin/rails reports:generate" --follow
blossom job:run:create --environment environment-100 --data job_run.yml --follow

With --job, use the saved definition without command or data overrides. With --environment, use exactly one of --command for a command with defaults or --data for structured execution settings. No saved Job is created. Keep the Environment identity in --environment, outside the data file.

job_run.yml:

job_run:
  command: printf hello
  size: inherit
  timeout_seconds: 120

Data files expand local environment variables; write $$VAR to pass a literal $VAR for expansion inside the application runtime.

By default, a Run matches your Environment’s largest Service requirements: the highest per-container CPU and memory among enabled Services, without multiplying replicas. The maxima may come from different Services. With no enabled Services, Blossom uses 0.25 vCPU / 256 MB. Each Run snapshots its size when accepted. The default execution timeout is 900 seconds. Optional size values are inherit, default (fixed 0.25 vCPU / 256 MB), small (0.5 vCPU / 1024 MB), medium (1 vCPU / 2048 MB), and large (2 vCPU / 4096 MB). For a specialized allocation, supply resources.cpu and resources.memory_mb instead of size; the two shapes cannot be combined. Blossom uses existing headroom or prepares Capacity within your Account Capacity budget. Preparation can wait up to 15 minutes and can be canceled before the command starts. The execution timeout begins separately. To allow more room ahead of time, use Spending Budget & Alerts or spending:update. Release overrides and schedules are not supported by this command.

With --follow, failed, timed-out, or canceled Runs return a nonzero CLI exit status. Without it, acceptance is not proof of successful execution.

blossom job:run:show --id job_run-100
blossom job:run:logs --id job_run-100 --follow
blossom job:run:cancel --id job_run-100

Launching a saved Job requires job:write; an ad hoc command requires environment:write. Reading output requires job:read, and canceling requires job:write. Job write access alone does not grant permission to execute an arbitrary Environment command.

Commands may change application data. Cancellation does not undo changes the command has already made.

On this page