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

James E. King III updated THRIFT-4795:
--------------------------------------
    Description: 
Travis CI does not have a facility to take data from one build job and easily 
get it to another.  In our build environment on Travis today we spin up a 
number of jobs to run cross test and they all have to do the same thing: make 
precross, then run a subset of tests.  The "make precross" is time-consuming.  
It would be better to "make precross" once and then spin off one build job per 
protocol to parallel process the cross tests.

CircleCI supports this behavior, and is the most likely candidate to experiment 
with:
https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-artifacts-among-jobs

  was:
Travis CI does not have a facility to take data from one build job and easily 
get it to another.  In our build environment on Travis today we spin up a 
number of jobs to run cross test and they all have to do the same thing: make 
precross, then run a subset of tests.  The "make precross" is time-consuming.  
It would be better to "make precross" once and then spin off one build job per 
protocol to parallel process the cross tests.

CircleCI supports this behavior, and is the most likely candidate to experiment 
with.


> Switch to a CI provider that supports artifact forwarding to optimize jobs
> --------------------------------------------------------------------------
>
>                 Key: THRIFT-4795
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4795
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process
>    Affects Versions: 0.12.0
>            Reporter: James E. King III
>            Assignee: James E. King III
>            Priority: Major
>
> Travis CI does not have a facility to take data from one build job and easily 
> get it to another.  In our build environment on Travis today we spin up a 
> number of jobs to run cross test and they all have to do the same thing: make 
> precross, then run a subset of tests.  The "make precross" is time-consuming. 
>  It would be better to "make precross" once and then spin off one build job 
> per protocol to parallel process the cross tests.
> CircleCI supports this behavior, and is the most likely candidate to 
> experiment with:
> https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-artifacts-among-jobs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to