Paste the YAML from your Jira ticket's deployment instructions and check it against the same rules the release pipeline enforces. Fix what's flagged, then copy the corrected block back into the ticket.
These are the checks the pipeline applies. Any key not listed below is rejected.
| Key | Required | Rule |
|---|---|---|
| env | Yes | List, subset of [dev, sit, prod], in that order, no duplicates. |
| client | Yes | List, values from laep, ukpn, ssen, resop, no duplicates. |
| db_snapshot | No | Object with enabled, meta_backup, non_meta_backup (booleans). |
| sql | No | List of { run, undo?, client? }. Paths: no leading /, no ... |
| pr | No | List of { url }. Full GitHub PR URL. |
| commit | No | List of { url }. Full GitHub commit URL (not a bare SHA). |
| script | No | List of { path, args?, params?, client? }. Path: no leading /, no ... |
| depends_on | No | List of Jira ticket keys this ticket deploys after. |
| pr.url | https://github.com/owner/repo/pull/123 |
| commit.url | https://github.com/owner/repo/commit/<sha> |
| sql.run / sql.undo | https://github.com/owner/repo/blob/<ref>/<path> or a repo-relative path |
Runs entirely in your browser. Mirrors DeploymentConfig in devops-automated-releases.