[JIRA] [bitbucket-plugin] (JENKINS-34694) BitBucket plugin requires Git polling enabled

2016-05-09 Thread thefriendlyco...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Phillips commented on  JENKINS-34694 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BitBucket plugin requires Git polling enabled  
 
 
 
 
 
 
 
 
 
 
I came across this seemingly related defect in the issue tracker, however the reporter appears to be reporting the opposite behavior from what I'm seeing here. Not sure how that is possible. 
That issue is reportedly caused by SHA1 hashes being excluded in certain situations. It does appear that the Bitbucket server edition does support disabling SHA1 hashes in their web hooks, however I have confirmed that our server has them enabled so I'm not convinced this is causing our problems. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [bitbucket-plugin] (JENKINS-34694) BitBucket plugin requires Git polling enabled

2016-05-09 Thread thefriendlyco...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Phillips created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34694 
 
 
 
  BitBucket plugin requires Git polling enabled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 bitbucket-plugin 
 
 
 

Created:
 

 2016/May/09 7:35 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kevin Phillips 
 
 
 
 
 
 
 
 
 
 
While testing the bitbucket Jenkins plugin with a locally hosted instance of BitBucket (aka: Stash) I discovered that web hooks from BitBucket server to Jenkins only work when the Jenkins jobs have polling enabled for the Git repository. Having only the BitBucket web hook trigger enabled does not appear to be sufficient. 
As a temporary hack I've simply enabled SCM polling triggers in my test jobs and intentionally left the polling interval empty, which essentially disables the SCM polling mechanism. Not only is this annoying, but it is very non-intuitive because it isn't obvious based on the logs and error messages that this is the root cause of the web hook triggering problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment