[WIP] Add alpha, canary, beta, release channels for Ember versions. #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
May 3, 2017 10:21
Collaborator
|
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. |
Gaurav0
force-pushed
the
master
branch
2 times, most recently
from
0d48aba to
3cbd712
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
canaryas 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...