-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Builld Tooling: Skip Chromium download in Travis by default #15712
Conversation
Truthy consideration: https://github.com/GoogleChrome/puppeteer/blob/c6c32491ec0a0209ab651c098e955d15c9305ab9/install.js#L23 Boolean( "false" ) === 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 can see that Chromium download is skipped on Travis for selected jobs. It’s surprising that impact is quite low. In general it should save a few seconds so let’s merge it.
Yeah, on average looks to be about 10 seconds savings per job. Not as great as I'd hoped either, but better than nothing for a simple adjustment. |
This happens because the wordpress/scripts package depends on Puppeteer, which results in attempts to download Chromium when running `npm install`. Once we use Puppeteer for end-to-end tests that can be run on Travis, we can enable the download again just for that stage. Related: WordPress/gutenberg#15712
We should use this env variable in the plugin build script as well. |
Yep, you can add it to the release script 👍 |
Related: #15667, #15159
This pull request seeks to skip Puppeteer's Chromium download in all Travis tasks except end-to-end containers. The proposed benefit is to help reduce the build time in non-end-to-end tasks, since the Chromium download can be time-consuming with its large size, and is unnecessary.
It may be possible to revert this optimization if and when a more general solution proposed in #15667 is implemented.
Testing Instructions:
Verify the Travis build passes.