CI/CD Integration with GitHub Actions, GitLab CI, and Jenkins: Configuration, Design Patterns, and Trade-Offs

1. Browser on the runner versus Grid/service infrastructure

The following table organizes the key choices and evidence for Browser on the runner versus Grid/service infrastructure. Use it together with the surrounding prose so the rows serve as a comparison aid rather than standalone rules.

2. Per-change smoke matrix versus scheduled broad matrix

A pull request benefits from fast evidence on the highest-risk browser lanes. A nightly or scheduled workflow can exercise more browsers, viewports, locales, or shards. Do not multiply dimensions mechanically: browser × OS × locale × viewport × shard can explode job count without increasing decision quality proportionally.

3. Fail-fast versus complete evidence collection

Fail-fast can save expensive capacity when one prerequisite failure makes every sibling meaningless—for example, dependency installation is broken globally. For a two-browser matrix, cancelling Firefox because Chrome found a browser-specific regression destroys useful comparison evidence. Prefer matrix fail-fast: false when each lane can teach you something independently, while still letting each lane’s test command fail normally.

4. Hosted versus self-hosted runners

Hosted runners offer disposable VM isolation and low maintenance. Self-hosted runners give control over browser versions, private network access, certificates, and hardware, but they create patching, secret, persistence, and concurrency obligations. A self-hosted browser runner should be treated like production infrastructure: least-privilege identity, clean workspaces, controlled browser/profile state, monitored capacity, and current runner software.

5. Cache dependencies, not mutable browser state

Pip caches can shorten dependency download time while the pinned requirements still define the environment. A cache is not a lockfile and should not hide version drift. Do not cache user-data directories, cookies, downloaded application files, or WebDriver session state across jobs. Those are test state and should start clean.

- uses: actions/setup-python@v7
  with:
    python-version: '3.13'
    cache: pip
- run: python -m pip install -r requirements.txt
# Do not cache Chrome/Firefox user profiles created by tests.

6. Mandatory gate versus nonblocking exploratory suite

A blocking gate needs stable ownership, deterministic data, bounded runtime, meaningful failure semantics, and an agreed browser support contract. An exploratory lane can surface a new browser/BiDi combination before it is reliable enough to block delivery, but “nonblocking” must not become “ignored forever.” Give it an owner, review threshold, and promotion/retirement rule.

7. Worked decision: 8-minute PR budget, two critical browsers, nightly localization

Use Chrome and Firefox smoke lanes per pull request with fail-fast: false and artifact retention on both. Keep four additional locale/viewport combinations in a scheduled workflow. If the smoke lanes regularly exceed eight minutes because both create heavyweight Grid clusters, move the browser capacity to a pre-provisioned private Grid or reduce startup overhead—not by dropping assertions or reusing dirty sessions.

8. Keep platform syntax subordinate to portable test design

GitHub cache keys, GitLab runner tags, and Jenkins agent labels are CI concerns. Browser options belong to Selenium configuration. Base URL and synthetic identity belong to environment/test configuration. Grid endpoint belongs to infrastructure configuration. A maintainable repository can change CI providers without rewriting page objects or business assertions.

Knowledge check

Official references and current-version notes

• Selenium 4.47 release notes
• Selenium downloads — current stable client and Grid versions
• GitHub-hosted runners reference
• GitHub Ubuntu 24.04 runner image inventory
• actions/checkout
• actions/setup-python
• actions/upload-artifact
• GitLab CI job artifacts
• GitLab CI/CD YAML reference
• Jenkins Pipeline tests and artifacts
• Jenkins Declarative Pipeline syntax