Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mxnet.incubator.apache.org
MIME-Version: 1.0
From: Indhu <indhubharathi@gmail.com>
Date: Tue, 10 Oct 2017 00:05:21 +0000
Message-ID: <CAC2KA1qyoFZKP2XySTYZuYp2qudjZ0-Jce75KbU=OfxO6i7+Zw@mail.gmail.com>
Subject: Incremental builds
To: "dev@mxnet.incubator.apache.org" <dev@mxnet.incubator.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c0d22e6ce564a055b261039"
archived-at: Tue, 10 Oct 2017 00:05:37 -0000

--94eb2c0d22e6ce564a055b261039
Content-Type: text/plain; charset="UTF-8"

Hi,

We all have the experience of making a small change in a PR and waiting for
a couple of hours or more for the continuous integration builds to finish.
This is because at the moment, all builds (even if it only fixes a typo in
a comment) is built from scratch as a clean build. I was wondering if we
can do incremental builds instead for changes to PRs. So, a clean build
will still happen when a PR is submitted for the first time. But every time
a change is made to the PR, we should be able to do an incremental build
from the previous build that was done for that PR. This will drastically
reduce the waiting time for developers.

I have an idea to do this which involves creating a separate directory in
jenkins slaves for each PR and doing the build for that PR under its own
directory. These directories can be created in EFS and they can be deleted
when the PR is closed. I'm wondering if there is a better/easier way to do
this. Please let me know if you know of any.

Thanks,
Indu

--94eb2c0d22e6ce564a055b261039--