CD & Release Orchestration

In a logged deployment there is a link to the associated job but the job's UI doesn't have a link to the deployment

Currently additional configuration needs to be added to account for the deploy marker job's status. Success and failure can be handled within the same job but canceled requires an additional job. These patterns are difficult to orbify because canceled requires adding the canceled job into a workflow

Facilitate programmatic interaction with historical deploy data via API

Links to the deployed resources, associated jira ticket, and other customized links being added to each deployment would help unify data around deployment in one place.

Currently, you can filter in the releases page based on the component name and environment. It would be great if you could filter the environment down to the namespace for those that deploy the same component to both a staging namespace and production namespace within the same environment.

Release markers are cool. But if I plan a release, I can't mark it as done without installed integration. I can only log releases. I would like to be able to plan a release and then eventually mark it as done from within my pipeline. Concrete proposal: Planning a release: No change Marking a release done: Add a parameter --plan-name to circleci run release log to support marking a planned release as done.