cops release projects commands let you manage the project configurations stored in cops.project.json. These commands are local operations — they read and write the config file and do not call any Atlassian APIs.
cops release projects list
cops release projects list
List all projects configured in
cops.project.json.Alias: cops release projects lsUsage
Flags
Output format:
table, json, or markdown.Output columns
project, default, source| Column | Description |
|---|---|
project | Project key |
default | true when this is the default project |
source | Config source: projects (multi-project map) or release (legacy top-level config) |
Examples
cops release projects show
cops release projects show
Show the resolved release configuration for a project. Displays all connection details and the number of configured gates.
Usage
Flags
Project key from the
projects map. Defaults to defaultProject or the top-level release block.Output format:
table, json, or markdown.Output columns
project, jiraProjectKey, jiraFixVersion, confluenceSpace, confluenceTitle, bitbucketProjectKey, bitbucketRepo, releaseBranch, bambooPlan, gateCountExamples
cops release projects migrate
cops release projects migrate
Migrate a legacy
cops.project.json (with a top-level release block) to the projects/defaultProject format. The migration wraps the existing release block under projects.<projectId> and sets defaultProject.Usage
Flags
Project ID to assign to the migrated legacy release configuration.
Preview the migration without writing any changes to disk.
Create a backup of
cops.project.json at cops.project.json.bak before writing the migrated config.Output format:
table, json, or markdown.Output columns
file, changed, dryRun, backupCreated, backupPath, detailsExit codes
| Code | Meaning |
|---|---|
0 | No migration was needed (config is already in projects format) |
2 | Migration was applied (changed) |
Examples
Related
cops release check
Run release gates for a configured project.
cops release summary
Cross-product release readiness summary.
