Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mxnet.incubator.apache.org
From: Meghna Baijal <meghnabaijal2017@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: MXNet: Run PR builds on Apache Jenkins only after the commit is
 reviewed
Message-Id: <4B2FF959-0A42-4637-9E78-26067E68A4CC@gmail.com>
Date: Mon, 11 Sep 2017 17:50:42 -0700
To: dev@mxnet.apache.org
archived-at: Tue, 12 Sep 2017 00:50:56 -0000

Hi All,=20
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 =E2=80=9Cok to build=E2=80=9D=
 before a PR build is triggered.=20

Do you think this approach would be helpful and we should move forward =
with it?

Thanks,
Meghna Baijal