This needs a bit of feedback / advice. The basic idea is that we need to be able to build addons when the Ember version is canary (or others).
To allow us to bust the cache I have set this up so that canary as an Ember version results in us caching for canary-2.15 (for this canary cycle). This means that for every new Ember release, we have to add the new version but also update the versions and configs for canary, alpha, beta, and release. I think this allows us to do what we want, and not have massive cache invalidation issues but I would really like @joostdevries to weigh in on this to confirm...
I'm wondering if an alternate solution -- which would solve other issues as well -- would be to somehow fingerprint the built addons. If that can't be done, this is a good fallback.
This needs a bit of feedback / advice. The basic idea is that we need to be able to build addons when the Ember version is
canary
(or others).To allow us to bust the cache I have set this up so that
canary
as an Ember version results in us caching forcanary-2.15
(for this canary cycle). This means that for every new Ember release, we have to add the new version but also update the versions and configs for canary, alpha, beta, and release. I think this allows us to do what we want, and not have massive cache invalidation issues but I would really like @joostdevries to weigh in on this to confirm...