CI/CD Integration with GitHub Actions, GitLab CI, and Jenkins: Core Concepts and Mental Model

1. A browser that launches in CI is not yet a trustworthy gate

Local tests inherit invisible machine state: installed browsers, cached Python packages, environment variables, open ports, user profiles, and files left by previous runs. CI is valuable because it can recreate a controlled environment from source. It becomes dangerous when the workflow silently depends on unrecorded runner state or discards the only evidence explaining a failure.

2. Commit → job → test command → evidence → gate

flowchart TD
 C[Commit or change] --> J[CI job]
 J --> D[Dependencies + browser / Grid]
 D --> S[Portable Selenium suite command]
 S --> W[WebDriver session]
 W --> A[AUT]
 S --> R[Exit status + result]
 S --> E[Evidence: capabilities/screenshots/logs]
 R --> G[Gate / report]
 E --> G[Gate / triage context]

The CI platform schedules the job and creates a workspace. Dependency setup creates the Python environment. Browser or Grid provisioning creates execution capacity. The same Selenium code should then create its WebDriver session, interact with the AUT, assert outcomes, and quit. The suite process returns a status code. CI interprets that status and separately stores evidence. A provider-specific YAML or Groovy file is therefore orchestration around a portable test contract.

3. Objects, state stores, and trust boundaries

The following table organizes the key choices and evidence for Objects, state stores, and trust boundaries. Use it together with the surrounding prose so the rows serve as a comparison aid rather than standalone rules.

4. Read-only preflight before the first test mutation

A CI test should start by making invisible state visible. Record Selenium and Python versions, the requested browser lane, the effective base URL, the commit/job identity when available, and—after session creation—the returned capabilities and session ID. Never dump the entire environment because it can contain secrets.

import json
import os
import platform
import selenium

safe_ci = {
    "selenium": selenium.__version__,
    "python": platform.python_version(),
    "browser_request": os.environ.get("LAB_BROWSER", "chrome"),
    "base_url": os.environ.get("LAB_BASE_URL", "http://127.0.0.1:8765"),
    "github_run_id": os.environ.get("GITHUB_RUN_ID"),
    "gitlab_job_id": os.environ.get("CI_JOB_ID"),
    "jenkins_build_tag": os.environ.get("BUILD_TAG"),
}
print(json.dumps(safe_ci, indent=2))

5. Exit status is the gate signal; artifacts are diagnostic context

Keep these channels separate. The test process returns zero only when the selected suite passed according to its assertion semantics. A screenshot or log cannot override a failing assertion. Conversely, artifact upload should normally run even when the test command fails, because the red run is precisely when operators need evidence.

portable command  -> exit 0  -> CI job may pass -> gate can be green
portable command  -> exit !=0 -> CI job fails   -> evidence still uploads
artifact upload   -> succeeds -> does not rewrite the test result

6. GitHub Actions, GitLab CI, and Jenkins are different orchestrators around the same contract

GitHub Actions expresses jobs and matrices in workflow YAML. GitLab CI uses .gitlab-ci.yml, runners, jobs, parallel:matrix, and artifact policies. Jenkins commonly uses a versioned Jenkinsfile with agents, stages, and post conditions. Their syntax differs; the Selenium suite should not. The portable boundary is: install dependencies → supply explicit configuration → run one command → preserve its status → collect evidence.

7. DevOps connection: evidence makes Selenium part of delivery control

A useful gate answers more than “did Chrome open?” It identifies the commit, runner image or agent class, Selenium version, actual browser/version, returned capabilities, selected environment, test result, and artifact bundle. With those facts, a remote operator can distinguish a product regression from a browser-image update, Grid incident, test defect, or CI provisioning problem.

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