Create and Verify Deployment
A 3-step recipe with Raygun. We can help you get access.
Recipe · 3 steps
Create and Verify Deployment
with Raygun · Software Release & Deployment Management
Create a deployment, read it back, and list its error groups.
- Record a new deployment for the application, capturing the supplied version and optional ownership and source-control metadata.
- Read the created deployment back by identifier to confirm it persisted and to capture its stored details.
- List the error groups attributed to the latest deployment so the release can be checked for newly introduced or reactivated errors.
What you'll need to have ready
- applicationIdentifier: The Raygun application identifier to record the deployment against.
- version: The version string of the deployment (1-128 characters).
- ownerName: The name of the person who triggered the deployment.
- emailAddress: The email address of the person who triggered the deployment.
- comment: A free-text comment describing the deployment.
- scmType: The source control system for the deployment commit.
- scmIdentifier: The source control commit identifier for the deployment.
For your developer
Arazzo workflow raygun:create-and-verify-deployment, 3 operations: create-deployment → get-deployment → list-error-groups-from-latest-deployment. Specs on APIs.io.