History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3417
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Steve Luo
Reporter: Alexey Shumkin
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

GitLab webhook setting is not available to descendants configuration

Created: 04/Jul/19 12:01 PM   Updated: 10/Mar/20 01:12 PM
Component/s: None
Affects Version/s: 9.0.10
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Operating System Linux 4.4.0-139-generic, amd64
JVM OpenJDK 64-Bit Server VM 1.8.0_111, Oracle Corporation
QuickBuild Version 9.0.10 - Sat May 18 10:49:01 UTC 2019

 Description  « Hide
QB server gives "Gitlab webhook setting not defined" and a build is not run when a configuration has a inherited GitLab webhook setting but does not override it.

1. Setup a PARENT configuration to accept GitLab webhooks.
2. See that a CHILD configuration has the parent's GitLab webhook setting.
3. Setup a GitLab project to run webhook request to QB server for the CHILD configuration
4. Test the webhook on GitLab.
5. See that QB server responds "Gitlab webhook setting not defined" (with no error status code due to QB-3416) and no new build is run.

6. Change the setup of the CHILD configuration to override the PARENT's GitLab webhook setting (press "Override" and then "Save")
7. Repeat step 4.
8. Observe that QB runs a new build request as expected

I'm expecting that a new build is run after step 4

 All   Comments   Work Log   Change History      Sort Order:
Change by Robin Shen [10/Mar/20 01:12 PM]
Field Original Value New Value
Assignee Robin Shen [ robinshine ] Steve Luo [ steve ]