Bug 1466634 - Webhook by branch is not triggered
Summary: Webhook by branch is not triggered
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-30 06:20 UTC by Jaspreet Kaur
Modified: 2023-09-14 04:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-05 15:16:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaspreet Kaur 2017-06-30 06:20:45 UTC
Description of problem: Currently our builds are setup for a particular branch in the git repo of the project.  But we have other branches people are working on.  When pushes are made to the other branches it triggers the webhook and starts a build.  It causes an excess of builds that are not needed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: 


Expected results: It should be triggered on particular branch


Additional info:

Comment 1 Ben Parees 2017-06-30 15:36:31 UTC
what git server are you using and which webhook?  The generic webhook does not distinguish by branch, but the github webhook(which also works with gogs) does, and the new gitlab and bitbucket webhooks being introduced in 3.6 will also distinguish by branch.

Comment 2 Ben Parees 2017-07-05 15:16:40 UTC
Closing due to lack of information.  Please reopen if you can provide additional details about which webhook you are using, but we have no plans to add branch-discrimination to the generic webhook.

Comment 3 Red Hat Bugzilla 2023-09-14 04:00:24 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.