CI/CD pipeline guides — integrate automated testing into your deployment pipeline and ship with confidence.
CI/CD
MegaLinter is a ready-to-use linting orchestrator that runs 100+ linters across all major languages and file types in a single Docker container. Instead of configuring Flake8, ESLint, hadolint, ShellCheck, markdownlint, yamllint, and a dozen others separately, MegaLinter runs all of them with one GitHub Actions workflow. It produces a unified
CI/CD
Hadolint is a Dockerfile linter that catches common mistakes, security antipatterns, and best-practice violations before your images are built. A misconfigured Dockerfile can produce bloated images, introduce vulnerabilities, or fail silently in production. Hadolint in CI prevents these issues from reaching your registries. Why Dockerfile Linting Matters Dockerfiles are often
CI/CD
Shell scripts are everywhere in software engineering — build scripts, deployment automation, CI pipelines, startup scripts, Docker entrypoints. They're also notoriously buggy. Word splitting, unquoted variables, unchecked error codes, and portability issues cause production failures that are difficult to reproduce and debug. ShellCheck catches these issues automatically before they
CI/CD
Ruff is a Python linter and formatter written in Rust that runs 10-100× faster than the tools it replaces. It implements rules from Flake8, isort, pylint, pyupgrade, and more — consolidating what used to be 5+ tools into one. For CI pipelines, Ruff's speed makes code quality gating essentially
CI/CD
Mypy is Python's most widely used static type checker. It catches type errors before runtime — wrong argument types, missing attributes, incorrect return types — the kind of bugs that slipped through Python's dynamic typing for decades. Integrating Mypy into CI transforms it from a developer convenience into
LLM Testing
The hardest thing about deploying LLM-powered features isn't building them — it's knowing whether they're getting better or worse. Prompt tweaks, model upgrades, retrieval changes: each one can improve performance on some inputs while degrading it on others. Braintrust gives you the infrastructure to measure
Deployment
Blue-green deployment reduces downtime risk by running two identical production environments — blue (live) and green (new). The switch happens at the router level, and rollback is instant: flip traffic back to blue. The testing challenge is making the cutover decision confidently: is green actually ready? The Blue-Green Testing Problem A
Security
OWASP ZAP is the benchmark for open-source web application security scanning. Most teams use it for baseline scans — but ZAP's real power is in its API, authenticated scanning, and deep CI/CD integration. This guide covers the complete picture. Active vs Passive Scanning Understanding the difference determines where
Security
Nuclei is a fast, template-based vulnerability scanner from ProjectDiscovery. Unlike ZAP or Burp, Nuclei runs predefined YAML templates — thousands of them for CVEs, misconfigurations, exposed panels, and default credentials. The template model makes it easy to write custom checks for your application's specific security requirements. Why Nuclei Speed
Security Testing
Dependency vulnerability scanning is table stakes for modern CI pipelines. A new critical CVE can drop at any moment, and without automated scanning, your pipeline will happily ship code with known exploitable vulnerabilities. Three tools dominate this space: Grype, Trivy, and OSV-Scanner. Each has different strengths, and the right choice
Test Reporting
JUnit XML is the lingua franca of test reporting. Originally a JUnit (Java) format, it's been adopted by every major test framework across every language. GitHub Actions, GitLab CI, Jenkins, CircleCI, and most other CI platforms can parse and display JUnit XML natively. Understanding how to generate and
Game Development
Godot 4 runs headlessly with --headless — no display required in CI. Combined with GUT's CLI runner, you can run your full test suite in GitHub Actions on every push. This guide covers setting up the CI pipeline, caching the Godot binary, running GUT tests, and reporting results. Key