diff mbox

[v4,4/6] .travis.yml: enable ccache for the builds

Message ID 1454434448-1535-5-git-send-email-alex.bennee@linaro.org
State New
Headers show

Commit Message

Alex Bennée Feb. 2, 2016, 5:34 p.m. UTC
Travis support ccache on a cache-per-branch basis. Given not much of the
build changes between pushes as well as the duplication in each build it
seems worthwhile enabling this.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
 .travis.yml | 1 +
 1 file changed, 1 insertion(+)

Comments

David Gibson Feb. 3, 2016, 5:59 a.m. UTC | #1
On Tue, Feb 02, 2016 at 05:34:06PM +0000, Alex Bennée wrote:
> Travis support ccache on a cache-per-branch basis. Given not much of the
> build changes between pushes as well as the duplication in each build it
> seems worthwhile enabling this.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Tested-by: David Gibson <david@gibson.dropbear.id.au>

From the build times, it doesn't look like this is buying us as much
as I might have hoped, still it's unlikely to hurt.

Do we know what the lifetime for the cache travis imposes?

> ---
>  .travis.yml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index 021eec7..4f09909 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -5,6 +5,7 @@ python:
>  compiler:
>    - gcc
>    - clang
> +cache: ccache
>  addons:
>    apt:
>      packages:
Alex Bennée Feb. 4, 2016, 3:09 p.m. UTC | #2
David Gibson <david@gibson.dropbear.id.au> writes:

> On Tue, Feb 02, 2016 at 05:34:06PM +0000, Alex Bennée wrote:
>> Travis support ccache on a cache-per-branch basis. Given not much of the
>> build changes between pushes as well as the duplication in each build it
>> seems worthwhile enabling this.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Tested-by: David Gibson <david@gibson.dropbear.id.au>
>
> From the build times, it doesn't look like this is buying us as much
> as I might have hoped, still it's unlikely to hurt.
>
> Do we know what the lifetime for the cache travis imposes?

AFAICT they last forever unless the user wipes the cache. They may have a
hidden heuristic to stop them growing too big but I don't know.

>
>> ---
>>  .travis.yml | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index 021eec7..4f09909 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -5,6 +5,7 @@ python:
>>  compiler:
>>    - gcc
>>    - clang
>> +cache: ccache
>>  addons:
>>    apt:
>>      packages:


--
Alex Bennée
diff mbox

Patch

diff --git a/.travis.yml b/.travis.yml
index 021eec7..4f09909 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -5,6 +5,7 @@  python:
 compiler:
   - gcc
   - clang
+cache: ccache
 addons:
   apt:
     packages: