Integracja Lighthouse z CI/CD

CI/CD stands for Continuous Integration and Continuous Delivery/Deployment. It's a modern approach to software development that focuses on automating various stages of the software lifecycle.

• Continuous Integration (CI): Developers frequently merge code into a central repository. Automated builds and tests run to detect issues early.
• Continuous Delivery (CD): After CI, code is automatically prepared for release, ensuring it's always in a deployable state.
• Continuous Deployment (CD): Takes CD a step further by automatically deploying every change to production, provided all tests pass.

CI/CD helps teams deliver updates faster and more reliably.

Integrating performance checks into your CI/CD pipeline is crucial for maintaining a fast website. Here's why:

• Catch Regressions Early: Automatically detect performance drops with every code change, before they reach users.
• Consistent Feedback: Get objective performance scores on every build, ensuring teams stay aware of their impact.
• Enforce Standards: Use performance budgets to fail builds if metrics fall below acceptable thresholds.
• Save Time: Automate manual auditing, freeing up developer time.

While you can run Lighthouse manually, Lighthouse CI (LHCI) is a dedicated tool designed to make automated performance auditing in CI/CD pipelines easy and effective.

LHCI provides a set of tools to:

• Collect Lighthouse reports across different branches and commits.
• Assert performance budgets against these reports.
• Display historical performance data.
• Integrate with various CI providers like GitHub Actions, GitLab CI, and Jenkins.

LHCI works through a command-line interface (CLI). You'll typically use two main commands:

• lhci collect: Runs Lighthouse audits on specified URLs and collects the results.
• lhci assert: Checks the collected results against predefined performance budgets and rules.

First, you usually install it globally or as a dev dependency:

LHCI uses a configuration file, often named lighthouserc.js or lighthouserc.json, to define how it should run. This file lives at the root of your project.

Here's a basic structure for lighthouserc.js, specifying where to run audits:

A key feature of LHCI is enforcing performance budgets. These are thresholds for metrics (like score, total byte weight, or largest contentful paint) that your site must meet.

You define budgets in the assert section of your lighthouserc.js. If any budget is violated, LHCI can fail your CI build.

GitHub Actions is a popular CI/CD platform integrated directly into GitHub repositories. You can easily add LHCI to your GitHub Actions workflow.

You'll create a YAML file (e.g., .github/workflows/lighthouse.yml) that defines the steps to run LHCI when certain events occur, like a pull request or a push to the main branch.

This allows automated checks before merging code.

Here's a simplified GitHub Actions workflow that sets up Node.js, installs LHCI, starts a server (if needed), collects audits, and asserts against budgets.

This workflow runs on every pull request to the main branch.

After LHCI runs in your CI/CD pipeline, it provides output directly in the build log. If budgets are set, the build will pass or fail accordingly.

• Passed: All performance budgets and assertions were met.
• Failed: One or more budgets were exceeded, indicating a performance regression.

For more detailed historical data and trend analysis, you can configure LHCI to upload reports to an LHCI server (either self-hosted or a cloud service).

Great job! In this lesson, we explored how to integrate Lighthouse into your CI/CD pipeline.

• We understood the importance of automating performance checks to prevent regressions.
• We learned about Lighthouse CI (LHCI) and its role in collecting audits and asserting budgets.
• We saw examples of configuring LHCI and integrating it with GitHub Actions.

By automating performance, you ensure your web projects remain fast and user-friendly over time. Keep exploring how to fine-tune your CI/CD setup for optimal results!