[jira] [Commented] (THRIFT-3850) All apache builds are failing when initiated from a github pull request

[ https://issues.apache.org/jira/browse/THRIFT-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326151#comment-15326151 ] ASF GitHub Bot commented on THRIFT-3850: Github user nsuke commented on the issue:

[GitHub] thrift issue #1024: THRIFT-3850: All apache builds are failing when initiate...

Github user nsuke commented on the issue: https://github.com/apache/thrift/pull/1024 A job is failing due to `make[2]: write error` and it seems to be reproducible. The same commit 4b7dbe3 as the current master worked for my travis account at the time of PR, though:

Re: [DISCUSS] Disable Github -> Jenkins pull request hook

I've disabled both jenkins jobs for now and have pushed pr 1024 [1] to get the baseline of where travis is at against the current trunk. anyone wanting to follow progress please watch THRIFT-3850 [2], ping or irc if interested in helping -Jake [1]: https://github.com/apache/thrift/pull/1024 [2]:

[GitHub] thrift pull request #1024: THRIFT-3850: All apache builds are failing when i...

GitHub user jfarrell opened a pull request: https://github.com/apache/thrift/pull/1024 THRIFT-3850: All apache builds are failing when initiated from a github THRIFT-3850: All apache builds are failing when initiated from a github pull request to Jenkins Disabled jenkins

[jira] [Commented] (THRIFT-3850) All apache builds are failing when initiated from a github pull request

[ https://issues.apache.org/jira/browse/THRIFT-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326124#comment-15326124 ] ASF GitHub Bot commented on THRIFT-3850: GitHub user jfarrell opened a pull request:

Re: [DISCUSS] Disable Github -> Jenkins pull request hook

No, I'm perfectly fine with Github and I'm not bound in any way to JIRA patches. I believe I made my point already. I just wanted to mention that should not repeat that discussion. From my feeling we should decide and act now. If that means that Jenkins and JIRA patches have to go, then fine.

Re: [DISCUSS] Disable Github -> Jenkins pull request hook

Jens, if the proposal is technically still pending, shall we resume it here or on the existing thread ? If I remember correctly, we were to choose between these two options. On Sun, Jun 12, 2016 at 12:45 AM Jens Geyer wrote: > > The interesting thing is that I made this

Re: [DISCUSS] Disable Github -> Jenkins pull request hook

The interesting thing is that I made this exact proposal just a few weeks ago, with exactly the same arguments. It was answered that we (can?) have JIRA patch pre-commit builds as well. $0,02 -Ursprüngliche Nachricht- From: Aki Sukegawa Sent: Saturday, June 11, 2016 5:26 PM To:

Re: [DISCUSS] Disable Github -> Jenkins pull request hook

Currently JIRA patches need manual verification that can to be error prone and/or tedious. It would make much sense to either enable the JIRA-patch-Jenkins integration or stop accepting JIRA patches. The latter seems reasonable to me, for the sake of simplicity and focus. On Sat, Jun 11, 2016 at