Re: submitting a hadoop patch doesn't trigger jenkins test run

2014-11-24 Thread Bernd Eckenfels
Hello, Am Mon, 24 Nov 2014 16:16:00 -0800 schrieb Colin McCabe : > Conceptually, I think it's important to support patches that modify > multiple sub-projects. Otherwise refactoring things in common > becomes a multi-step process. This might be rather philosophical (and I dont want to argue the

Re: submitting a hadoop patch doesn't trigger jenkins test run

2014-11-24 Thread Vinayakumar B
As I mentioned jn HADOOP-11293, This is not issue of any script, but the execution time. Actually jenkins is getting triggered. But since changes involves multiple projects, executing tests for all those projects taking more time. currently in jenkins if build time is more than 5 hours, then that

[jira] [Created] (HADOOP-11331) rename shell daemon functions to specify java

2014-11-24 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-11331: - Summary: rename shell daemon functions to specify java Key: HADOOP-11331 URL: https://issues.apache.org/jira/browse/HADOOP-11331 Project: Hadoop Common

Re: submitting a hadoop patch doesn't trigger jenkins test run

2014-11-24 Thread Colin McCabe
Multi-subproject patches used to work. If they don't work now, it is probably a bug in test-patch.sh that we should fix. The code there is written expecting multi-project changes, but maybe it doesn't get much of a workout normally. Conceptually, I think it's important to support patches that mo

[jira] [Created] (HADOOP-11330) KMSClientProvider should use PseudoDelegationTokenAuthenticator as the Authenticator when security is disabled to improve performance

2014-11-24 Thread Dian Fu (JIRA)
Dian Fu created HADOOP-11330: Summary: KMSClientProvider should use PseudoDelegationTokenAuthenticator as the Authenticator when security is disabled to improve performance Key: HADOOP-11330 URL: https://issues.apach