[jira] [Resolved] (HADOOP-16514) Current/stable documentation should link to Hadoop 3

2019-09-10 Thread Akira Ajisaka (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-16514. Resolution: Fixed > Current/stable documentation should link to Hadoop 3 >

[jira] [Reopened] (HADOOP-16514) Current/stable documentation should link to Hadoop 3

2019-09-10 Thread Akira Ajisaka (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-16514: > Current/stable documentation should link to Hadoop 3 >

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2019-09-10 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1255/ [Sep 9, 2019 2:07:11 AM] (jhung) YARN-9764. Print application submission context label in application [Sep 9, 2019 3:44:07 AM] (bharat) HDDS-2087. Remove the hard coded config key in ChunkManager (#1409)

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-10 Thread Duo Zhang
Actually the job for testing PR is here... https://builds.apache.org/job/hadoop-multibranch/ I've added the 'Change requests' option(seems I have the permission...), and then clicked the 'Scan Now', the job for PR-1404 has been scheduled

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

2019-09-10 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/440/ [Sep 9, 2019 2:20:51 AM] (jhung) YARN-9764. Print application submission context label in application [Sep 9, 2019 7:30:20 AM] (jhung) YARN-9820. RM logs InvalidStateTransitionException when app is

[jira] [Created] (HADOOP-16555) Update commons-compress to 1.19

2019-09-10 Thread Wei-Chiu Chuang (Jira)
Wei-Chiu Chuang created HADOOP-16555: Summary: Update commons-compress to 1.19 Key: HADOOP-16555 URL: https://issues.apache.org/jira/browse/HADOOP-16555 Project: Hadoop Common Issue

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-10 Thread Steve Loughran
On Tue, Sep 10, 2019 at 9:07 AM 张铎(Duo Zhang) wrote: > Nits: You can change the jenkins job config to not trigger pre commit build > for stale PRs if only the base branch is changed. By default, either the PR > itself changed, or the base branch is changed, the branch sources plugin > will both

[jira] [Resolved] (HADOOP-15747) warning about user:pass in URI to explicitly call out Hadoop 3.2 as removal

2019-09-10 Thread Steve Loughran (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-15747. - Resolution: Won't Fix nobody is complaining about change; seems that people read the

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-10 Thread Duo Zhang
OK, the indexing is finished [Tue Sep 10 14:25:07 UTC 2019] Finished branch indexing. Indexing took 15 min So maybe 30 minutes is better... And we really should cleanup the stale PRs and branches... 张铎(Duo Zhang) 于2019年9月10日周二 下午10:20写道: > Actually the job for testing PR is here... > >

[jira] [Resolved] (HADOOP-16551) The changelog*.md seems not generated when create-release

2019-09-10 Thread Zhankun Tang (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang resolved HADOOP-16551. --- Resolution: Fixed Close this since revert HADOOP-16061 has fixed it. > The changelog*.md

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-10 Thread Akira Ajisaka
Thanks all for the discussion. I'm +1 for adding PR template and I wrote a patch long ago: https://issues.apache.org/jira/browse/HADOOP-15184 I'm interested in "test this", "retest this", etc. I'll file a jira for this feature. -Akira On Thu, Sep 5, 2019 at 4:05 AM Sean Busbey wrote: > We

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-10 Thread Duo Zhang
Nits: You can change the jenkins job config to not trigger pre commit build for stale PRs if only the base branch is changed. By default, either the PR itself changed, or the base branch is changed, the branch sources plugin will both trigger a build. You can add a Change requests option, and