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

Recipe for separate Lighthouse job #40

Open
paulirish opened this issue Mar 27, 2020 · 1 comment
Open

Recipe for separate Lighthouse job #40

paulirish opened this issue Mar 27, 2020 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@paulirish
Copy link
Contributor

@Snugug shared a cool Github Actions pattern he's using to run multiple jobs in parallel but only after the project has been built. Basically it's a combo of the needs job property combined with uploading/downloading artifacts.

it gives two benefits:

  1. you can do jobs in parallel, to get all CI finishing faster.
  2. a separate 'commit status' item for Lighthouse. Sam sez he likes this especially depending on how he did his budgets. maybe some are required and others more optional.

https://github.com/chromeos/static-site-scaffold/blob/master/.github/workflows/nodejs.yml shows it in use. pretend the commented-out job is still there. ;)


users of this action probably would like to use this kinda pattern.

@alekseykulikov
Copy link
Member

Hey @paulirish, thank you for sharing!
At Treo, we came up with the same pattern. It allows us to have separate statuses for build and LH results, and test different URL groups in parallel.
I will add a recipe with an example for this case.

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

No branches or pull requests

2 participants