Skip to content

Use nodejs buildpack directly (instead of via the emberjs buildpack) #2806

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

Merged
merged 1 commit into from
Sep 20, 2020

Conversation

jtgeibel
Copy link
Member

Since #2657 we build the frontend twice during a deploy. It seems that
the nodejs buildpack (pulled in by the emberjs buildpack) is running
our build script so lets just depend on that directly because it is
actively supported by Heroku.

r? @JohnTitor

Since rust-lang#2657 we build the frontend twice during a deploy. It seems that
the nodejs buildpack (pulled in by the emberjs buildpack) is running
our build script so lets just depend on that directly because it is
actively supported by Heroku.
@jtgeibel
Copy link
Member Author

This also appears to drop the size of the compiled slug from ~270M to ~90M!

Copy link
Member

@JohnTitor JohnTitor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also appears to drop the size of the compiled slug from ~270M to ~90M!

Wow, that's a great improvement! Looks reasonable to me.

@JohnTitor
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Sep 20, 2020

📌 Commit 2307bd6 has been approved by JohnTitor

@bors
Copy link
Contributor

bors commented Sep 20, 2020

⌛ Testing commit 2307bd6 with merge 6ba7e75...

@bors
Copy link
Contributor

bors commented Sep 20, 2020

☀️ Test successful - checks-travis
Approved by: JohnTitor
Pushing 6ba7e75 to master...

@bors bors merged commit 6ba7e75 into rust-lang:master Sep 20, 2020
@jtgeibel jtgeibel deleted the use-nodejs-buildpack-directly branch September 21, 2020 00:31
@jtgeibel
Copy link
Member Author

This also appears to drop the size of the compiled slug from ~270M to ~90M!

Wow, that's a great improvement!

Strangely, I did not observe a similar drop on staging. I looked into some recent deploys, more info in #2809.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants