1081579 - Cache stored s3 git clone tarball of gaia

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia, defect)

Comment 1

[Julien Wajsberg [:julienw]]

Do you want to cache accross builds, or only accross runs in one build?

Be careful:
* when you get the cache, properly set the saved timestamp, otherwise Make will never want to update it even if it should
* be careful with the branches
* should you also cache other downloaded stuff?

Comment 2

[James Lal [:lightsofapollo]]

Re-purposing this bug to only cache the s3 tarball we use in taskcluster to warm the git clone (this is a no brainer and entirely within the docker container setup rather then in gaia) see https://bugzilla.mozilla.org/show_bug.cgi?id=1067626 for some more details on how TC actually does caching.

Comment 3

[James Lal [:lightsofapollo]]

Attachment: https://github.com/mozilla-b2g/gaia/pull/25059

Greg you feel up for reviewing this? First place we are really using the cache... From my less then scientific measurement this saves 30s~ of overhead but more importantly it removes 1gig of network traffic (reducing traffic helps at higher capacity nodes)

Comment 4

[James Lal [:lightsofapollo]]

Ah note that is PR is based on earlier work so see the second commit only.

Comment 5

[Greg Arndt [:garndt]]

Comment on attachment 8503728 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/25059

r+ with just a couple of questions on GH to be clarified.

Comment 6

[James Lal [:lightsofapollo]]

Now that I have had some time to think about I think the cache "resources" is the wrong name... (also this becomes a scoping problem I found out later) so I think renaming it to "gaia" is specific enough. Ideally we use one cache for all of gaia (or version the cache if we totally change what is stored in it)

Comment 7

[James Lal [:lightsofapollo]]

https://github.com/mozilla-b2g/gaia/commit/fd7aaa083530304ad1e4706eb0020d43f866eed1