website logo
Sign upLogin
⌘K
πŸš€ Getting started
Introduction
Echoes fundamentals
Understanding Echoes data
Developer guide
Configuration guides
βš™οΈ CONFIGURATION
Outcomes
Initiatives
Members
Teams
πŸ”Œ INTEGRATIONS
Source code managers
Issue trackers
Incident management
Compatibility matrix
πŸ“Š REPORTS
Organization health
DORA metrics
πŸ€– API
Introduction
Authentication
Releases
Incidents
Efforts
DORA metrics
πŸ”” NOTIFICATIONS
Email report
Slack notifications
πŸ‘€ ACCOUNT
Users & Roles
Single sign-on
Linking identities
Billing
πŸ₯· ADVANCED
Echoes IP addresses
Scoped publishing
Changelog
Docs powered byΒ archbeeΒ 
7min

Releases

Introduction

The releases API lets you declare deployment to Echoes. This information is then leveraged in multiple places:

  • In the Releases page, to show the timeline of releases and their content.
  • In Lead time, to compute the last segment of the development cycle.
  • In Deployment frequency, to compute the frequency without relying on tags alone.

An API Keys is required in order to use the Signal Releases API.

API interface

Get a cake by its ID
GET
Params
Body Parameters
id
required
String
ID of the cake to get

Usage example in GitHub CI/CD

YAML
|

Content of the release.sh script

Shell
|

ο»Ώ

Get a cake by its ID
GET
Params
Body Parameters
id
required
String
ID of the cake to get
Updated 22 Nov 2022
Did this page help you?
Yes
No
UP NEXT
Incidents
Docs powered byΒ archbeeΒ 
Create Releases