-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add script to automatically update plunker bundle #913
Conversation
771f71e
to
738aff3
Compare
|
||
matrix: | ||
fast_finish: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish I had known this option existed long ago...
Is there a way to only run this for |
@hansl can you review this PR? |
* The bundle will be used to load a Plunker Demo of Angular Material 2. | ||
*/ | ||
|
||
const spawn = require('child_process').spawnSync; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Name the function the same, so in this case spawnSync
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That setting is only for branches. We still run this on every PR (including this one).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah gotcha. I thought that Jeremy meant, that it shouldn't run in other branches. Will add a check for the environment variable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually we're creating a firebase for this right now, and we'll add the login key to Travis. We'll let you know what key to use :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I'm available on Slack, if there're any questions (I got one :D).
When deploying to firebase, we overwrite the current hosting and loose the old bundles (like for tags)
We need a way to pull the old files or find another approach for hosting
Created a new firebase instance called |
@devversion Use the environment variable |
@hansl I think the way he's doing it know is fine; it's explicitly checking whether it is a PR |
Yeah I think both ways are actually fine. However I'll change it to address @hansl's comment :) |
@hansl are you capturing this in your build changes? |
No, but it should probably be a followup PR on it. |
b4b779f
to
e7f3906
Compare
@hansl @devversion can you two connect to update this based on the new build? |
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
Going to replace this with a Gulp task #1222 |
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
* Gulp task to create a bundle, which includes all components and all Angular 2 packages * Designed to run inside of the Plunker Template * Task to deploy to firebase (as per angular#913) Closes angular#913
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Adds a script to automatically update the plunker bundle by using the Angular CLI with Production Mode.
The firebase hosting will contain files:
HEAD_bundle.js
(Latest Bundle for each commit)2.0.0-alpha.6
(Bundle for that tag)Open Points:
We need a way to pull the old files or find another approach for hosting
Please give some thoughts @jelbourn