[prev in list] [next in list] [prev in thread] [next in thread] 

List:       enlightenment-devel
Subject:    [E-devel] CI and branch building: optimizing your build times
From:       Mike Blumenkrantz <michael.blumenkrantz () gmail ! com>
Date:       2018-08-01 14:37:09
Message-ID: CAHwmOzcFPN3BorQszAMtRfm7uezDF4OB6Y1C6LZKK8L6xpgcDQ () mail ! gmail ! com
[Download RAW message or body]

Hello,

As some people are already aware, new pushes to dev branches in git are now
built by travis (on an hourly basis). This allows patches to be fully
tested (including unit tests!) before landing them or submitting them for
review.

One thing to keep in mind is that our CI builds now make heavy use of
caching to speed up builds. This means that any time a branch is built more
than once, the build will be significantly faster.

Caches in CI are based on the branch name. This means that as long as you
keep using the same dev branch name, e.g., devs/myname/citest, you will
always reuse the cache and continue to receive the speedups that it
provides.

Regards,
Mike
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[prev in list] [next in list] [prev in thread] [next in thread]