mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed
Date Wed, 13 Sep 2017 21:31:39 GMT
Side note:

There is no "we". The below should say something like "I would like to
propose...", or "As part of my work at <Corporation>, I would like to
propose..." if it's coming from a team at your day job and you don't want
to hog all the glory :)

If it truly is "we", then the email should end with the "we" that the email
is from. For example a release announcement from me would say "We are proud
to release" and would end with "Hen, on behalf of the Apache MXNet project".


On Mon, Sep 11, 2017 at 17:50 Meghna Baijal <>

> Hi All,
> We would like to initiate a change in the way the PR builds are being
> triggered. At the moment, every time a Pull Request is created, a build
> gets triggered on Jenkins. Additional builds also get triggered due to
> changes to the same PR.
> Too many PR builds leads to resource starvation and very long queues and
> long build times. Hence we would like to add some checks where a human
> reviewer manually marks it to something like “ok to build” before a PR
> build is triggered.
> Do you think this approach would be helpful and we should move forward
> with it?
> Thanks,
> Meghna Baijal

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