www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@apache.org>
Subject Re: Hadoop CI with alternate architectures.
Date Tue, 31 May 2016 14:33:38 GMT

Since infra-dev appears to be staying out of the conversation, I’d recommend filing a JIRA
under INFRA to get their attention.

Thanks.

> On May 23, 2016, at 9:57 PM, MrAsanjar . <afsanjar@gmail.com> wrote:
> 
> back to top:
> Any suggestion from apache builds team on how to proceed? 
> I have at least one ppc64le build server readied to contribute to the build pool
> 
> On Thu, May 19, 2016 at 10:27 AM, MrAsanjar . <afsanjar@gmail.com> wrote:
> Thanks Steve,
> Adding builds@apache.org  to the list.
> I do realize the primary concern is the post build, fixing build breaks and bugs.
> Le me assure you that is our primary objective as well, fixing CI issues.
> 
> On Wed, May 18, 2016 at 12:46 PM, MrAsanjar . <afsanjar@gmail.com> wrote:
> Allen/Tsuyoshi
> Thank you for your prompt replies. Well, let me fix CI for ppc architecture issue once
and for all :)
> We at OpenPOWER foundation have at least one Power system with the following configuration
available:
> Power8, 4 cores, 32 G mem, 500 G HD.  
> Would that be sufficient to start? 
> 
> On Wed, May 18, 2016 at 10:29 AM, Allen Wittenauer <aw@apache.org> wrote:
> 
> 
>         That’s really a question for infrastructure-dev@apache.org . They manage the
ASF build infrastructure which Apache Hadoop and lots of other projects utilize.  (Bigtop
uses something custom, which I think is funded by Cloudera.)
> 
>         Once it is registered with builds.apache.org, it’s just a matter of us enabling
a Jenkins job for it. I suspect we’ll likely do it like we have done other architectures
in the past: set up a nightly job that people will need to cognizant of.  Adding it to precommit
would likely be too much and/or require some significant Yetus work to support reports from
multiple hosts.
> 
>         FWIW:
> 
>                 * We have a Mac mini which, ironically, I thought I’d see if I could
get a nightly job running on while I type this.
>                 * We have a dedicated Windows box which appears to be completely screwed
up.
>                 * In the past, I think it was IBM that hinted that they would be willing
to give ASF a PowerPC box but that offer seems to have disappeared.
> 
> > On May 18, 2016, at 7:52 AM, Tsuyoshi Ozawa <ozawa@apache.org> wrote:
> >
> > Hi Asanjar,
> >
> > Thanks for your contribution! I'm ashamed to say, but I don't know how
> > to change the build machine.
> >
> > Adding "to" Allen, who is a PMC of Yetus project. Hey Allen, do you
> > know how to add Power based Jenkins slave(s) to Apache Hadoop CI?
> >
> > Thanks,
> > - Tsuyoshi
> >
> > On Wed, May 18, 2016 at 11:18 PM, MrAsanjar . <afsanjar@gmail.com> wrote:
> >> moving up.. :)
> >>
> >> On Thu, May 12, 2016 at 12:45 AM, MrAsanjar . <afsanjar@gmail.com> wrote:
> >>
> >>> I am writing this email to reduce mishaps similar to the issue reported
by
> >>> JIRA https://issues.apache.org/jira/browse/HADOOP-11505. In a nutshell,
> >>> an x86 specific
> >>> performance enhancement broke Hadoop build on Power and SPARC architecture.
> >>> To avoid similar issues in future, could I offer my help here, as a
> >>> OpenPOWER foundation member.
> >>> For example, we could contribute a Power based Jenkins slave(s) to Apache
> >>> Hadoop CI. As we  have successfully done similar contribution to Apache
> >>> Bigtop CI in past
> >>> https://ci.bigtop.apache.org/computer/docker-slave-ppc-1/. Thus, we could
> >>> catch any regressions earlier in Hadoop  development cycle. I'd appreciate
> >>> community's guidance on this.
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> 
> 
> 
> 


Mime
View raw message