Re: Where do we track our Jenkins stuff

[Sean Busbey]

Hi folks!

Any response here? The notice from infra about projects needing to update
for Maven and Java had a three day migration period.

I'm happy to just make something up, but I want to make sure it's useful
for the other person or people who currently update build stuff.

-- 
Sean Busbey
On Aug 5, 2016 08:36, "Sean Busbey"  wrote:

> Apologies, but I haven't managed to figure out where we track our changes
> to Jenkins.
>
> The ASF build infra has some changes to Java and Maven installations
> coming and a fair number of Hadoop related jobs need to be updated.
>
> If I take on doing said updates, do I track it in a JIRA? Or is there some
> particular mailing list thread or a wiki page or something?
>
> --
> Sean Busbey
>

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

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/

[Aug 5, 2016 8:31:11 AM] (aajisaka) HDFS-10715. NPE when applying 
AvailableSpaceBlockPlacementPolicy.
[Aug 5, 2016 10:57:53 AM] (varunsaxena) YARN-5429. Fix return related javadoc 
warnings in yarn-api (Vrushali C
[Aug 5, 2016 4:05:49 PM] (rohithsharmaks) YARN-5333. Some recovered apps are 
put into default queue when RM HA.
[Aug 5, 2016 5:27:34 PM] (wangda) YARN-4091. Add REST API to retrieve scheduler 
activity. (Chen Ge and
[Aug 5, 2016 5:43:35 PM] (wangda) YARN-4888. Changes in scheduler to identify 
resource-requests explicitly
[Aug 5, 2016 5:55:29 PM] (junping_du) YARN-5470. Differentiate exactly match 
with regex in yarn log CLI.
[Aug 5, 2016 7:43:36 PM] (naganarasimha_gr) YARN-4624. NPE in 
PartitionQueueCapacitiesInfo while accessing Schduler
[Aug 5, 2016 11:32:44 PM] (weichiu) HADOOP-13353. LdapGroupsMapping getPassward 
shouldn't return null when
[Aug 6, 2016 3:22:02 AM] (iwasakims) HADOOP-13418. Fix javadoc warnings by JDK8 
in hadoop-nfs package.




-1 overall


The following subsystems voted -1:
asflicense unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.tracing.TestTracing 
   hadoop.security.TestRefreshUserMappings 
   hadoop.yarn.logaggregation.TestAggregatedLogFormat 
   
hadoop.yarn.server.nodemanager.containermanager.queuing.TestQueuingContainerManager
 
   hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.client.TestApplicationClientProtocolOnHA 
   hadoop.yarn.client.api.impl.TestYarnClient 
   hadoop.mapreduce.v2.hs.server.TestHSAdminServer 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-compile-javac-root.txt
  [172K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-checkstyle-root.txt
  [16M]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-patch-pylint.txt
  [16K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-patch-shellcheck.txt
  [20K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-patch-shelldocs.txt
  [16K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/whitespace-eol.txt
  [12M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/whitespace-tabs.txt
  [1.3M]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/diff-javadoc-javadoc-root.txt
  [2.2M]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [312K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
  [24K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
  [36K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [268K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
  [16K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-hs.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-nativetask.txt
  [124K]

   asflicense:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/125/artifact/out/patch-asflicense-problems.txt
  [4.0K]

Powered by Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org



-
To unsubscribe, e-mail

Re: Where do we track our Jenkins stuff

[Chris Nauroth]

Hello Sean,

Thank you for bringing this up.  The lack of response could indicate that we’re 
not doing enough recently to maintain our Jenkins jobs.  I’m not aware of any 
existing up-to-date tracking for these jobs.  Starting a wiki page to catalog 
all of our jobs sounds like a great step toward improving on this.

Thank you for your help with this!

--Chris Nauroth

On 8/6/16, 6:27 AM, "Sean Busbey"  wrote:

Hi folks!

Any response here? The notice from infra about projects needing to update
for Maven and Java had a three day migration period.

I'm happy to just make something up, but I want to make sure it's useful
for the other person or people who currently update build stuff.

-- 
Sean Busbey
On Aug 5, 2016 08:36, "Sean Busbey"  wrote:

> Apologies, but I haven't managed to figure out where we track our changes
> to Jenkins.
>
> The ASF build infra has some changes to Java and Maven installations
> coming and a fair number of Hadoop related jobs need to be updated.
>
> If I take on doing said updates, do I track it in a JIRA? Or is there some
> particular mailing list thread or a wiki page or something?
>
> --
> Sean Busbey
>

Re: Where do we track our Jenkins stuff

[Sean Busbey]

Okay, I'll get something together today.

Thanks for the response Chris!

-- 
Sean Busbey
On Aug 6, 2016 10:48, "Chris Nauroth"  wrote:

> Hello Sean,
>
> Thank you for bringing this up.  The lack of response could indicate that
> we’re not doing enough recently to maintain our Jenkins jobs.  I’m not
> aware of any existing up-to-date tracking for these jobs.  Starting a wiki
> page to catalog all of our jobs sounds like a great step toward improving
> on this.
>
> Thank you for your help with this!
>
> --Chris Nauroth
>
> On 8/6/16, 6:27 AM, "Sean Busbey"  wrote:
>
> Hi folks!
>
> Any response here? The notice from infra about projects needing to
> update
> for Maven and Java had a three day migration period.
>
> I'm happy to just make something up, but I want to make sure it's
> useful
> for the other person or people who currently update build stuff.
>
> --
> Sean Busbey
> On Aug 5, 2016 08:36, "Sean Busbey"  wrote:
>
> > Apologies, but I haven't managed to figure out where we track our
> changes
> > to Jenkins.
> >
> > The ASF build infra has some changes to Java and Maven installations
> > coming and a fair number of Hadoop related jobs need to be updated.
> >
> > If I take on doing said updates, do I track it in a JIRA? Or is
> there some
> > particular mailing list thread or a wiki page or something?
> >
> > --
> > Sean Busbey
> >
>
>
>

Proposal: Drop all project specific labels.

[Gav]

Hello All!

Please take a look at:-

https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels

I do not see a need any longer for the project specific labels.


I think we can drop all of these:-


HDFS, MapReduce, Pig, Falcon, Tez, ZooKeeper.

(yahoo-not-h2 and ubuntu labels are already being discussed to drop)


Unless I hear objections within the next 5 days, I'll go ahead and move
everyone
using those to the Hadoop label.

I am not subbed to your list , replies to builds@ cc: to me please.

For those of you that configure jenkins and/or buildbot builds and are not
subbed to the builds@ list, I encourage you to do so.

Thanks

Gav...