Skip to content
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

Merged
merged 2 commits into from
May 20, 2019

Conversation

aduth
Copy link
Member

@aduth aduth commented May 17, 2019

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.

@aduth aduth added the [Type] Build Tooling Issues or PRs related to build tooling label May 17, 2019
@aduth aduth mentioned this pull request May 17, 2019
14 tasks
@aduth aduth requested a review from gziolo May 17, 2019 18:52
@gziolo
Copy link
Member

gziolo commented May 20, 2019

Sharing from another PR for comparison:
631014E7-CB9E-4F50-933F-2B1C90118C42

@gziolo
Copy link
Member

gziolo commented May 20, 2019

This branch:

D0E7BC0B-E101-4BB2-BFD0-47BA65014ECE

Copy link
Member

@gziolo gziolo left a 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.

@aduth
Copy link
Member Author

aduth commented May 20, 2019

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.

@aduth aduth merged commit 9d56b8b into master May 20, 2019
@aduth aduth deleted the update/travis-puppeteer-download branch May 20, 2019 12:22
swissspidy added a commit to ampproject/amp-wp that referenced this pull request May 21, 2019
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
@youknowriad youknowriad added this to the 5.8 (Gutenberg) milestone May 24, 2019
@youknowriad
Copy link
Contributor

We should use this env variable in the plugin build script as well.

@gziolo
Copy link
Member

gziolo commented May 27, 2019

Yep, you can add it to the release script 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Build Tooling Issues or PRs related to build tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants