Re: PR builds are currently failing due to a known issue

[Daniel Pono Takamori]

Unfortunately we won't be able to enable all the Groovy methods for
security reasons.  Fortunately the Beam team has found some work
arounds for this so I'm cc'ing them to connect you to figure out how
to get around this issue.

Jason, if you could point the MXNet folks to your builds repo so they
could take a look and ask questions, that would be great!

On Thu, Sep 28, 2017 at 10:59 AM, Naveen Swamy  wrote:
> Please revert this change until Apache Infra approve all the required
> scripts? I don't think we should let the PR builds continue to fail this
> long.
>
> On Wed, Sep 27, 2017 at 3:57 PM, Meghna Baijal 
> wrote:
>
>> Hi All,
>> This is just to let everyone know that PR #8034 is breaking the Apache
>> MXNet PR builds for the moment. The master branch is not affected by this.
>>
>> This PR makes changes to the Jenkinsfile and some script approvals are
>> required from the Apache infra team. I have opened a JIRA ticket for the
>> same -https://issues.apache.org/jira/browse/INFRA-15176 <
>> https://issues.apache.org/jira/browse/INFRA-15176> and we are in the
>> process of resolving it.
>>
>> I will update this thread once the issue is fixed.
>>
>> Thanks,
>> Meghna Baijal
>>
>>

MXNet Build Services

[Daniel Pono Takamori]

Hello MXNet Team,
I wanted to send an email to check in on your build services and make
sure we're on the same page when it comes to the MXNet project and
Apache Infrastructure.  As I'm sure you are aware the ASF has over 200
active projects and plenty more subprojects that we shepard. Coming
from the infra side of things, this can often make it overwhelming to
understand and work with the multitude of needs these projects
possess.

When MXNet was onboarding into the the Incubator I tried my best to
facilitate the transition and as such made myself readily available to
your team members who asked for it.  This might have been a mistake as
I didn't make it clear that I was giving priority to your project to
get you up to speed.  As it stands now it seems that your team might
think I'm the only infra member which can help them!  On the contrary
we have a great team of 5 people who are equally if not more
knowledgeable than I am.

The places to reach our team are on Hipchat, where we can try to be
real time but given workloads sometimes that's not possible, email
us...@infra.apache.org for general infrastructure questions and
bui...@apache.org for specific questions.  But most importantly is the
JIRA instance https://issues.apache.org/jira/browse/INFRA  This is
where you can file tickets when you need help with things and we will
be able to look at them and work on them as our workload enables us to
(keep in mind we cannot respond instantly to each of 200 projects so
you'll have to bear with us).

Now onto the more technical side of things.  As you are hosting your
own build nodes and connecting them to our jenkins we can only do the
adding and renaming, etc.  Recently with
https://issues.apache.org/jira/browse/INFRA-15114  it came up that
there is some backend tooling at Amazon that Apache Infra was
completely unaware of.  It would definitely help all of us involved if
you keyed us into the overall design of your setup that way it didn't
seem like every single request in Hipchat was of utmost urgency.
Browsing the dev@mxnet list I haven't been able to find much
information about the build setup so I'm not sure where those
conversations are happening.

To summarize:
1).  The ASF is a huge organization and cannot give preferred
treatment to projects.
2).  I (Pono) am not the only Infra member that can help you
3). JIRA is the best place to get our teams attention for work items
4).  Discussion about your build system should be more transparent and
certainly include the Infra team.

Thanks for listening and good luck Incubating!
-Daniel Pono Takamori

incubator-mxnet builds not working?

[Daniel Pono Takamori]

Hey there, we've got https://travis-ci.org/apache/incubator-mxnet
which was recently added in to our Org.  In the move from org to org,
it seems something is off since the builds are kicking off on PRs.

I've disabled and reenabled the builds for this repo, but it doesn't
seem to be triggering anything.  I've manually kicked off a build
https://travis-ci.org/apache/incubator-mxnet/builds/203107794 but
normal requests don't seem to be building.

Any ideas on what's happening?

-Pono on behalf of ASF Infra

Fwd: Stop automated message from Apache Git Service

[Daniel Pono Takamori]

We just transferred the mxnet repo to the Apache Organization, that's
what's causing the increased mail to dev@mxnet.  There needs to be a
log for all events on Github, and as such these are sent to the dev@
list.  If there is consensus in moving the mail to another list
(creating another is possible by the PMC [0]) then please file an
Infra JIRA ticket [1].

Cheers,
Pono from Infra

[0] - https://whimsy.apache.org/officers/mlreq
[1] - https://issues.apache.org/jira/projects/INFRA/summary

On Fri, Jul 28, 2017 at 12:46 PM, Yutian Li  wrote:
> I noticed the emails are sent to a mailing list. So it can't be turned
> off for a single person unless I quit the mailing list?
>
> On Fri, Jul 28, 2017 at 12:38 PM, Yutian Li  wrote:
>> Hi,
>>
>> Is it possible to stop automated message for every pull request or
>> issue to a repo that is linked on GitHub?
>>
>> I'm receiving these emails from g...@git.apache.org
>>
>> Thanks,
>> Yutian

Re: MXNet -> Apache Migration proposal

[Daniel Pono Takamori]

This looks great Ly.  On Monday we can transfer the main repo over and
then you can change the builds to point to the official repo.  I'll
make a clone of the website next week so we can do a similar thing to
test building the website and then we can publish it to
mxnet.incubator.apache.org.  Once we have that worked out we can move
forward with transferring the domain to our control.

Have a great weekend everyone!

On Fri, Jul 7, 2017 at 6:07 PM, Dominic Divakaruni
 wrote:
> great stuff!! glad to see this getting close!
>
> On Fri, Jul 7, 2017 at 3:47 PM, Ly Nguyen  wrote:
>>
>> We have successfully validated that merges and pull requests against an
>> Apache fork of MXNet runs successfully on builds.apache.org:
>>
>> https://builds.apache.org/blue/organizations/jenkins/incubator-mxnet-master2/detail/master/13/pipeline
>>
>> https://builds.apache.org/blue/organizations/jenkins/incubator-mxnet-master2/detail/PR-3/1/pipeline
>>
>> We have also added a dummy nightly run to be populated with builds and
>> test
>> cases after migration, as discussed. We can now move forward with the
>> migration to Apache and I recommend the following steps:
>> - [ ] Add Pono as owner
>> - [ ] Pono adds Apache git hooks to MXNet repo
>> - [ ] Change source control of Apache Jenkins jobs to point to MXNet repo,
>> verify a run is successful
>> - [ ] Change MXNet org to Apache, verify a run is successful, mxnet.io
>> still building
>> - [ ] Start docs build to mxnet.apache.org
>> Note that one kink to iron out is that PR build statuses aren’t being
>> updated. Here’s a ticket to follow:
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=25=INFRA=detail=INFRA-14540
>>
>>
>> On Sat, Jul 1, 2017 at 9:15 PM, shiwen hu  wrote:
>>
>> > 1. The `mxnet directory` is a directory on the current CI server. He
>> > contains the necessary files, including library dependencies, data files
>> > needed for testing, compiling scripts needed, and so on.You can find Mu
>> > Li
>> > and ask him to copy from the current Ci
>> > 2.Graphics Driver downlaod from
>> > http://www.nvidia.com/Download/index.aspx
>> > 3.Luanch is a small program. As long as you run it, you should be able
>> > to
>> > see what to do at a glance
>> >
>> > 2017-07-02 10:03 GMT+08:00 Naveen Swamy :
>> >
>> > > @yajiedesign
>> > > we are building a new slave to be used in Apache Infra, the
>> > > instructions
>> > > here
>> > > https://gist.github.com/yajiedesign/40b3809b51a1706d353e9129071b14
>> > fb
>> > > to setup a new slave from scratch is insufficient(probably outdated),
>> > > we
>> > > ran into quite a bit of problem setting up OpenBlas and OpenCV(those
>> > > instructions were missing) though we were able to get through these
>> > > problems we anticipate further problems.
>> > > since we want to move our Infrastructure to Apache by the end of next
>> > week
>> > > we have paused the effort of setting up a Windows slave and testing
>> > > the
>> > > Linux slaves that are already setup.
>> > >
>> > > Is it possible for you to update those instructions? meanwhile, we
>> > > have
>> > > requested Mu Li to create an AMI out of the existing slave.
>> > >
>> > > Can I also request you to provide instructions on how to create pip
>> > package
>> > > for Windows? currently, 0.10 version does not have windows pip
>> > > package?
>> > >
>> > > Thanks, Naveen
>> > >
>> > >
>> > >
>> > > On Sat, Jul 1, 2017 at 12:14 AM, shiwen hu 
>> > wrote:
>> > >
>> > > > what problem with windows ci?
>> > > >
>> > > > 2017-07-01 9:06 GMT+08:00 Ly Nguyen :
>> > > >
>> > > > > This week's summary:
>> > > > > 1. Wrote FAQ and publicized CI wiki
>> > > > > 2. Plan was to complete migration by end of next week
>> > > > > 1. Spent 1.5 days trying to set up Windows slave - was not
>> > > successful
>> > > > > and would find it more productive to create an AMI from currently
>> > > running
>> > > > > slaves. Mu says a running Windows slave is not necessary for
>> > migration
>> > > > but
>> > > > > that means we would be losing Windows coverage.
>> > > > > 2. The goal for this week was to ensure that PRs, merges,
>> > nightlies
>> > > > > against the fork trigger builds that pass. There were a lot of
>> > hurdles.
>> > > > > Many items had to happen in sequence and depended on others’
>> > schedules.
>> > > > > Namely,
>> > > > > 1. accepted invitation to be committer on Monday morning
>> > > > > 2. received Apache account Tuesday morning
>> > > > > 3. got access to Jenkins & repo Wednesday morning
>> > > > > 4. filed tickets for the Infra team to add webhooks which
>> > > > > was
>> > > > > addressed this morning https://issues.apache.org/
>> > > jira/browse/INFRA-14472
>> > > > > 5. Apache builds of all projects including MXNet’s were
>> > > > > not
>> > > > > happening because of some infra issue