Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions content/en/docs/deployment/general/mendix-pipelines/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -351,10 +351,6 @@ Mendix Pipeline failure notifications only send if the user who triggered the Me

Mendix Pipelines time out if they run for more than three hours. In other words, if the cumulative execution time of all operations in your Mendix Pipeline exceeds this limit, the Mendix Pipeline will fail.

Existing Mendix Pipeline users can view previously created webhooks that trigger Mendix Pipelines from [Teamserver push (Git)](/developerportal/deploy/webhooks/#teamserver-push-git) by clicking **Webhooks** in the [navigation pane](/developerportal/#navigation-pane).

These webhooks can be safely deleted without affecting the functionality of your Teamserver push (Git) triggers and are not visible to first-time Mendix Pipeline users.

### Known Issues and Limitations

* **Mendix Pipelines maintenance behavior** – Mendix Pipeline runs are not picked up and executed if the Mendix Pipelines functionality is undergoing maintenance.
Expand Down
6 changes: 0 additions & 6 deletions content/en/docs/deployment/general/webhooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,12 +161,6 @@ Make sure to use the correct key names when using this payload information to ca

## Teamserver Push (Git)

{{% alert color="info" %}}
This webhook is not visible to first-time [Mendix Pipeline](/developerportal/deploy/mendix-pipelines/) users.

Existing Mendix Pipeline users can view this webhook, but it can be safely deleted without affecting the functionality of the Teamserver push (Git) triggers.
{{% /alert %}}

When you push a model change to the [Git Team Server](/developerportal/repository/team-server/), and the webhook responds to the event **Teamserver push (Git)**, request content is sent to the configured endpoint. The request content contains a payload with the following format:

```json
Expand Down
Loading