thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James E. King, III (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (THRIFT-4153) Add CI build jobs that do nothing except rebuild the docker image(s) if necessary to avoid timeouts
Date Wed, 05 Apr 2017 14:48:41 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James E. King, III resolved THRIFT-4153.
----------------------------------------
    Resolution: Won't Fix

Travis has no facilities to put in a barrier or initialization phase job like this, so I am
closing this out as won't fix.

> Add CI build jobs that do nothing except rebuild the docker image(s) if necessary to
avoid timeouts
> ---------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-4153
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4153
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process
>    Affects Versions: 0.10.0
>         Environment: Travis CI
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Critical
>
> In the Travis CI environment if someone modifies a docker image, the build system has
to rebuild the image.  This is expensive and takes a while, and usually causes one of the
first five build jobs to fail.  In addition the image is rebuilt multiple times.
> The improvement here is to have a set of docker image verificaion/rebuild jobs that run
before the other build jobs.  Each one will simply load up the docker image, see if it needs
to be rebuilt, and rebuilt it.  If it is possible to express dependencies between Travis CI
jobs, then we can add dependencies so that once the docker image has been rebuilt, certain
jobs can start running.
> This is typically seen when someone needs to rev the docker image.  Their pull request
causes docker images to be rebuilt, and it can timeout a build job.  Then their build fails,
and the build job that queues behind it will have to rebuild the docker image back to what's
based on master, so it will probably timeout too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message