Bitbucket event fired
This trigger takes in the contents of a Bitbucket event and presents it as an output event
This trigger fires when an event from Bitbucket is received.
The payload will be wrapped in an additional map called
needs to be unwrapped at the step level in order to use it; see the example below.
For more details about the specific event payloads, check out the documentation.
- From Bitbucket, open the repository where you want to add the webhook.
- Click the Settings link on the left side.
- From the links on the Settings page, click the Webhooks link.
- Click the Add webhook button to create a webhook for the repository.
- On the Add new webhookpage, enter a Title with a short description.
- Copy the URL from the Relay trigger
- Enter that URL into the URL field.
- If necessary, update the Triggers field. By default, the trigger for the webhook is a repository push, as demonstrated by the Repository push field. If you want additional or different actions to trigger the webhook, click Choose from a full list of triggers. You will see a list of all the event types that can trigger the webhook.
- After you entered all the necessary information for your webhook, click Save.
For more details about setting up webhooks, check out the documentation.
parameters: event_payload: description: "The full json payload from the incoming Bitbucket event" triggers: - name: bitbucket-event source: type: webhook image: relaysh/bitbucket-trigger-event-fired binding: parameters: event_payload: !Data event_payload steps: - name: dump-payload image: relaysh/core spec: event_payload: !Parameter event_payload input: - mkdir -p /bitbucket/workflow - "ni get | jq .event_payload > /bitbucket/workflow/event.json" - cat /bitbucket/workflow/event.json