Add automated publishing of weekly alpha releases to NPM #19441
Merged
Conversation
This file contains 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
rwjblue
force-pushed
the
automated-alpha-releases
branch
from
149e9ad
to
f0e9afa
Compare
kategengler
approved these changes
Mar 1, 2021
By default the ember-cli blueprint uses ember-try to download the `npm pack` result of the most recent caanry build from Amazon S3 (this is usually setup to run in that addon's CI configuration). Unfortunately, some organizations have security restrictions **preventing** access to the internet during CI jobs. They often have customized NPM mirrors that do work (otherwise how would they ever build / test JS code), but block access to the rest of the internet. Up until this change, those organizations simply **could not** be early testers of our canary builds. This change adds a new CI job to auto-publish a new `-alpha.x` release to NPM once a week (on Mondays). This will allow folks to leverage their normal `npm install` infrastructure to be able to test canary Ember builds once a week (though we could in theory decide to make more publish). However, since the process is automated these alphas will not include changelog entries. It is theoretically possible that we would prefer to leverage this infrastructure for testing addons against published tags (instead of using `ember-source-channel-url`), but that would reduce our speed of identifiying regressions.
rwjblue
force-pushed
the
automated-alpha-releases
branch
from
f0e9afa
to
0079b11
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default the ember-cli blueprint uses ember-try to download the
npm packresult of the most recent canary build from Amazon S3 (this is usually setup to run in that addon's CI configuration). Unfortunately, some organizations have security restrictions preventing access to the internet during CI jobs. They often have customized NPM mirrors that do work (otherwise how would they ever build / test JS code), but block access to the rest of the internet. Up until this change, those organizations simply could not be early testers of our canary builds.This change adds a new CI job to auto-publish a new
-alpha.xrelease to NPM once a week (on Mondays). This will allow folks to leverage their normalnpm installinfrastructure to be able to test canary Ember builds once a week (though we could in theory decide to make more publish). However, since the process is automated these alphas will not include changelog entries. It is theoretically possible that we would prefer to leverage this infrastructure for testing addons against published tags (instead of usingember-source-channel-url), but that would reduce our speed of identifying regressions.