Is the load artificially high because there's such a backlog due to other reasons? Many may be triggering trivial changes to kick off another build attempt (I have).
Do new PR changes actually stop the old build or do those go to completion? I realize they show on the PR as a new build has started, but are the old builds/tests always interrupted? On Mon, Sep 11, 2017 at 6:12 PM Naveen Swamy <[email protected]> wrote: > +1 > > Even a small change in the PR is initiating a new build, I think this is > needless and not serving any good purpose until a reviewer has looked into > the PR. This is also adding unnecessary load on the mxnet build pipeline > and slaves. > > Thanks, Naveen > > > On Mon, Sep 11, 2017 at 5:50 PM, Meghna Baijal <[email protected] > > > wrote: > > > 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 > > > > > > > > >
