Re: No action in response to a PR, even with hooks all apparently set

g states that it recognized the incoming webhook. > > I don't get your answer though - how did you finally solve the problem? > > Thanks! > Andreas > > Am Donnerstag, 27. Oktober 2016 19:21:00 UTC+2 schrieb Benson Margulies: >> >> I found the bottom of thi

Re: No action in response to a PR, even with hooks all apparently set

I found the bottom of this one, too. I should never have turned on the elaborate github-specific whitelisting plugin, but rather read the doc: https://github.com/KostyaSha/github-integration-plugin/blob/master/docs/Configuration.adoc -- You received this message because you are subscribed to th

Re: No action in response to a PR, even with hooks all apparently set

And on the PR status page, here's my PR, but it has no builds, and clicking on 'rebuild' gets me 'Build not found'. > #293: WS-1008: basic changes required. > > Head SHA: ae9d5233a8c23d60bd173fb793990bd41328c62e Author: benson Issue > updat

No action in response to a PR, even with hooks all apparently set

My project has 'Hooks with Persisted Data' as the mechanism, and Pull Request Opened and Commit Changed as the triggers. I can see the hooks being fired in the github hook area. see that Jenkins returned this very boring 200 response. *Date:* Thu, 27 Oct 2016 16:33:26 GMT*Server:* Jetty(9.2.

Re: TLS/ssl problems talking to github enterprise

I solved this for myself. It turns out that the stock Docker image for java8, used by jenkins, has it's own special approach to trust stores. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving ema

Re: TLS/ssl problems talking to github enterprise

Please also note the last exception: Can't process check (Can't find appropriate client for github repo ) org.jenkinsci.plugins.github.internal.GHPluginConfigException: Can't find appropriate client for github repo

TLS/ssl problems talking to github enterprise

Our GFE instance uses a certificate from an annoying certificate authority (godata). To get Jenkins to talk to it at all, I had to create a trust store with their intermediate certificates. And now, basic operations work, everything tests out on the configuration page, etc. But when a pull req