Gearset

You can set an outgoing webhook as part of continuous integration jobs in Gearset. This is documented <a href="https://docs.gearset.com/en/articles/2652073-outgoing-webhooks-in-continuous-integration-jobs">here</a>.

The standard payload available for CI outgoing webhooks contains information about the CI job and run.

{   "job": {     "name": "dev to uat"   },   "run": {     "status": "Succeeded",     "type": "Deployment",     "start_date_utc": "2020-02-24T16:37:41.899337Z",     "end_date_utc": "2020-02-24T16:39:06.689647Z",   } }

We include the <code>X-Gearset-Event</code> header to specify which event the outgoing webhook was triggered by. For continuous integration job runs, this is set to <code>ci_job_run</code> .

In the standard payload we provide the following:

Run status — <code>string</code>  that can be <code>Error</code>, <code>Succeeded</code>,  or <code>Failed</code>.

Run type — <code>string</code>  that can be <code>Deployment</code>  or <code>Validation</code>.

Run start date — <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

Run end date —  <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

- Job name — <code>string</code>. 
- Run status — <code>string</code>  that can be <code>Error</code>, <code>Succeeded</code>,  or <code>Failed</code>. 
- Run type — <code>string</code>  that can be <code>Deployment</code>  or <code>Validation</code>. 
- Run start date — <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>. 
- Run end date —  <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

If you have any questions about setting up your outgoing webhooks, please <a href="https://docs.gearset.com/en/articles/2288721-contacting-gearset-support">reach out to our team</a> using the in-app chat.

An example of a payload format for your CI jobs

Standard CI outgoing webhook payload

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Standard CI outgoing webhook payload

Example payload format

Payload format