mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco de Abreu <>
Subject Re: Move to new CI
Date Wed, 06 Dec 2017 08:14:09 GMT
Thanks for your feedback, Bhavin.

I've uploaded the documents to Google Docs:
- Auto scaling:
- Security design:

Please note that these documents are still WIP.


Am 06.12.2017 8:11 vorm. schrieb "Bhavin Thaker" <>:

Hi Marco,

Thanks for your work on the CI.

Is it possible/ok to share the docs via googledocs link until you get write
permissions for the apache wiki page?

Bhavin Thaker.

On Tue, Dec 5, 2017 at 4:06 PM, Marco de Abreu <
> wrote:

> Hello MXNet community,
> as discussed in
> and tracked at, we've
> decided
> to switch to a new CI running Jenkins and move away from the current setup
> running under Within the past weeks, me and my team
> have
> been working on setting up the new CI.
> We've reached a state which is, besides a few structural changes described
> in, compatible to the
> MXNet repository. I'd like to make the transition within the next days and
> thus request a review on my PR.
> I would like to point out, that at this stage, we're only migrating to the
> new CI. This means we're in control of the master, can start and stop
> slaves as desired, don't rely on Apache Infra-tickets and thus increase
> stability and reaction time. Just to set some expectations: During my
> I've noticed seg-faults, flaky tests and other irregular build failures
> like they're already happening on the current CI setup. These are not
> related to the CI itself, but we're going to look into these issues after
> the initial migration has been completed. While the new CI is running,
> we'll work on implementing reactive auto scaling to avoid any queue times.
> I would appreciate some feedback and I'd like to hear if there's anything
> you'd like to have in the new CI. Additionally, I've created a few design
> documents regarding auto scaling and security design, but unfortunately,
> I'm not able to share them yet due to permission issues on the MXNet wiki.
> As soon as they're available, I'll send a follow-up email.
> Looking forward to your feedback.
> Best regards,
> Marco

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message