| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Warning |
|---|
Throughout Summer’23 we plan to make Outcoming WebHooks obsolete and substitute it with full-fledged Release Automation Explained. Existing hooks will keep on operating. At some point we will remove ability to create new hooks / clone existing. And after decent graceful period we will fully deprecate old WebHooks functionality. |
Topics
| Table of Contents |
|---|
Overview
...
|
Overview
Webhooks are aimed to integrate the Release Management app with other software in your organization to create a single and integrated workspace. Typical use cases are the following:
...
For each history items, the details could be reviewed: - full HTTP request with headers and full HTTP response. This will help to spot and solve any potential problems.
...
Important (!): IPs whitelisting
Webhooks are outcoming requests from our servers. If you want to receive these requests in your internal network (probably protected by Firewall) you need to while list IPs of our 3 nodes in different availability zones, namely:
...
From the user list, find a user from step 2, click on the “configure” icon (the wrench and screwdriver) next to the user name
Underneath the user’s full name and description is a section labelled “API Token”. Click on the “Show API Token” button. This will reveal the API token you need to provide when triggering a job by URL
With this information, you can now create a URL that looks like this:
http://user_name:your_tocken@your_jenkins.com/job/your_job_name/build?token=your_auth_tocken_from_step_3
More use cases
...
...
Tip: Still have questions or need hands-on advice?