Sentry with YAML
Learn more about:
YAML parameters for Sentry
Name | Type | Description |
---|---|---|
action Required | String | The name of the action. |
type Required | String | The type of the action. Should be set to SENTRY . |
organization_slug Required | String | The slug of the organization the release belongs to. |
integration_hash Required | String | The ID of the integration. |
version Required | String | The version identifier of the release. |
environment Required | String | The environment you’re deploying to. |
organization_slug Required | String | The short name of your organization. |
deploy_url | String | The optional url that points to the deploy. |
release_url | String | An optional commit reference. |
projects Required | String[] | The list of project slugs that are involved in this release. |
repository | String | If Sentry is integrated with repository provider, you can enter the project slug here. You can use the $BUDDY_REPO_SLUG variable as well. |
YAML example for Sentry
actions:
- action: "Sentry Action"
type: "SENTRY"
trigger_time: "ON_EVERY_EXECUTION"
organization_slug: "buddyworks"
organization_name: "Buddy"
version: "${BUDDY_EXECUTION_REVISION}"
environment: "$env"
release_url: "${BUDDY_EXECUTION_REVISION_URL}"
deploy_url: "${BUDDY_EXECUTION_URL}"
repository: "$BUDDY_REPO_SLUG"
projects:
- "java"
- "my_proj"
integration_hash: "5ddb7c180fb38be67bd78a88a"
variables:
- key: "env"
value: "linux"
Last modified on February 15, 2023