commons-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sesuncedu <>
Subject [GitHub] commons-compress issue #43: COMPRESS-413 : Improved build performance with t...
Date Mon, 26 Jun 2017 15:01:14 GMT
Github user sesuncedu commented on the issue:
    Travis has some nice properties, especially when working with forks. It's very easy to
enable travis for a fork, so CI can be done before a PR goes in.
     Travis can also run really quickly, but only when tuned properly, and when the system
is not running at capacity. If the stars are aligned, you can get every job in a big 'ol 
matrix running in parallel (each container build gets 2 cores and max 4GB of memory), which
is  nice if they're free.  The critical thing is to be using the container environments and
not the VM, as the startup time is tiny.  The annoying thing about Travis is that the default
environment is running Ubuntu 12.04, which is well past its LTS date. The trusty (14.04) container
is *still* marked as beta, despite being on a production level update cycle (set group to
edge for that real beta experience). The 12.04 containers all have to do a lot of package
replacement on startup, which takes away some of the benefits of having a container ). I kept
the home server on 12.04 until the end of LTS because Travis, then went  to xenial (16.04)
which is the current LTS, and has nice things like proper zfs (hey- an apac
 he connection). 
    Hudkins farms in my mental model usually seem to be more congested, but there are good
reasons not to believe that. 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message