Bug 1500731
Summary: | Bitbucket Server 5.4 Webhook push sends X-Event-Key repo:refs_changed. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> |
Component: | Build | Assignee: | Ben Parees <bparees> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | aos-bugs, xiuwang |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The BitBucket build trigger webhook did not handle older versions of the webhook payload.
Consequence: Builds could not be triggered by older versions of BitBucket Server.
Fix: Add support for the older payload format.
Result: Builds can be triggered by older versions of BitBucket.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:16:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ruben Romero Montes
2017-10-11 11:46:27 UTC
according to the doc: A user pushes one or more commits to a repository. This payload, with an event key of repo:push, provides the following fields: Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/5cfb55eb7ddaba7a5ebb55347e5790f974ece2f8 add bitbucket v5.4 support bug 1500731 https://bugzilla.redhat.com/show_bug.cgi?id=1500731 Verified on ocp 3.7[1] with bitbucket 5.4 server.When push to repo,bitbucket webhook could trigger build successully without error. [1]openshift v3.7.0-0.188.0 kubernetes v1.7.6+a08f5eeb62 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188 |