Best of CI/CD — December 2025

  1. 1
    Article
    Avatar of theregisterThe Register·25w

    Zig quits GitHub, gripes about Microsoft's AI obsession

    The Zig Software Foundation is migrating from GitHub to Codeberg, citing declining engineering quality and neglected critical bugs in GitHub Actions. A CPU-spinning bug in GitHub's safe_sleep script went unaddressed for years despite being reported multiple times, causing CI runners to hang indefinitely. Zig's president criticized Microsoft's AI focus as distracting from core platform maintenance, pointing to what he calls 'vibe-scheduling' where jobs run seemingly at random. The move reflects broader developer concerns about GitHub's priorities, with Codeberg doubling its membership since January as other projects also consider leaving.

  2. 2
    Article
    Avatar of goserverlessServerless·23w

    CI/CD for monorepos

    Serverless Framework Pro's CI/CD solution supports deploying multiple services from a single monorepo. Services should be organized in separate subdirectories off the root, with each service configured with the same app and org settings. After initial deployment via CLI, connect your GitHub or BitBucket repository and configure branch-to-stage mappings for automated deployments. Advanced features include selective deployments (only redeploy when specific service code changes) and dependency-based deployments (redeploy when dependent services or shared code folders are modified). This approach provides flexibility to deploy only what's needed based on code changes.

  3. 3
    Article
    Avatar of programmingdigestProgramming Digest·24w

    No code reviews by default

    Raycast's engineering team operates without mandatory code reviews, allowing engineers to push directly to the main branch and request reviews only when needed. This trust-based approach emerged from their early startup days and scaled with their distributed team. They prioritize rapid iteration through daily internal releases, dogfooding changes within 24 hours, and shipping public updates every two weeks. Code reviews are still used selectively for unfamiliar code areas, database migrations, or onboarding new team members. The team relies on post-commit notifications, quick video calls, and continuous integration to maintain quality while avoiding the bottlenecks of traditional pull request workflows.

  4. 4
    Video
    Avatar of primeagenThePrimeTime·23w

    Github continues to Downfall

    GitHub Actions has suffered from critical bugs for years, including a poorly implemented sleep function that causes infinite loops, consuming entire CPUs and costing users thousands of dollars. A simple fix submitted in 2024 took over a year to merge despite the bug causing CI jobs to hang indefinitely. The codebase shows questionable engineering decisions, from using ping commands as sleep alternatives to busy-wait loops that waste compute resources. These neglected issues have led projects like Zig to abandon GitHub entirely for alternative platforms.

  5. 5
    Article
    Avatar of gitlabGitLab·25w

    Deploying the world's largest GitLab instance 12 times daily

    GitLab deploys code to GitLab.com up to 12 times daily using their own CI/CD platform, handling millions of developers without downtime. The deployment pipeline uses progressive rollouts through staging and production Canary environments (5% traffic), followed by full staging and production deployments. Key technical challenges include managing hybrid infrastructure (Helm charts for containers, Omnibus packages for Gitaly), handling database migrations with backward compatibility, and maintaining multi-version compatibility during deployments. The expand-migrate-contract pattern ensures safe schema changes, while post-deploy migrations run only after multiple successful deployments to minimize rollback risks. This approach validates GitLab's deployment features at massive scale before customers use them.

  6. 6
    Video
    Avatar of t3dotggTheo - t3․gg·22w

    The Github Tax (I can't believe they actually did this...)

    GitHub announced a new fee structure charging 0.008 cents per minute for using self-hosted runners with GitHub Actions, even when compute runs on third-party platforms like Blacksmith or Depot. This pricing change affects all self-hosted runners and has sparked widespread criticism from developers who view it as penalizing users for choosing alternatives to GitHub's infrastructure. The fee applies regardless of whether jobs run for seconds or minutes, and critics argue GitHub is extracting revenue from an ecosystem while failing to invest in improving Actions' performance, reliability, and observability. The change has intensified concerns about GitHub's direction under Microsoft ownership and lack of clear leadership.

  7. 7
    Article
    Avatar of laravelLaravel·22w

    How We Built Laravel Wrapped

    Laravel's team built Laravel Wrapped in under two weeks, creating personalized year-in-review experiences for 55,000+ users. The project aggregated data across Cloud, Forge, and Nightwatch using CSV exports and custom Artisan commands, generated AI-powered insights via batched OpenAI prompts, and built an interactive React/Inertia frontend with drag-and-drop sharing capabilities. Key technical challenges included syncing React components with server-rendered OG images, implementing real-time chat using Laravel MCP, and managing deployment speed through Laravel Cloud's preview environments and serverless Postgres. The team leveraged Laravel Boost extensively for AI-assisted development, enabling rapid iteration and same-day fixes during launch.

  8. 8
    Video
    Avatar of techworldwithnanaTechWorld with Nana·21w

    From Non IT to Lead DevOps Engineer | The Exact Roadmap

    A civil engineer from Nigeria transitioned to a Lead DevOps Engineer role in the UK within 9 months through structured learning, strategic career planning, and hands-on practice. Starting with zero IT experience while working retail night shifts and facing visa pressure, he chose DevOps for its high salary threshold enabling visa sponsorship. After scattered learning attempts, he enrolled in a structured DevOps bootcamp, passed the CKA certification, and built comprehensive projects demonstrating integrated tool knowledge. His deep conceptual understanding of CI/CD optimization, Docker layer caching, and Kubernetes fundamentals helped him excel in technical interviews. He negotiated between two offers, choosing the role with modern tech stack (Kubernetes, Terraform, Ansible) over legacy tools, resulting in 25% higher salary. On the job, he immediately added value by building production Kubernetes clusters from scratch and implementing security scanning pipelines, earning a 10% raise within his first year.

  9. 9
    Article
    Avatar of freekFREEK.DEV·23w

    A Production-Ready Laravel Architecture with Traefik and FrankenPHP

    A guide demonstrates how to deploy a high-performance Laravel application using Laravel Octane with FrankenPHP as the application server, Traefik as a reverse proxy, and Docker Compose for orchestration. The architecture focuses on production readiness with automated workflows and optimized performance for PHP applications.

  10. 10
    Article
    Avatar of netflixNetflix TechBlog·22w

    How Temporal Powers Reliable Cloud Operations at Netflix

    Netflix reduced transient deployment failures from 4% to 0.0001% by migrating cloud operation orchestration from Spinnaker's homegrown system to Temporal's durable execution platform. The original Clouddriver service suffered from complex internal orchestration, instance-local state, and unreliable retry logic. By implementing cloud operations as Temporal workflows with activities, Netflix eliminated tight coupling between services, removed thousands of lines of custom orchestration code, and gained automatic retries, state persistence, and better observability. The migration used abstraction layers and dynamic configuration to transparently onboard all applications within two quarters.

  11. 11
    Video
    Avatar of dreamsofcodeDreams of Code·22w

    Doppler is without a doubt my favorite secrets management platform

    Doppler is a secrets management platform that provides a centralized solution for storing, managing, and syncing secrets across local development, multiple environments, CI/CD pipelines, and production deployments. It eliminates the limitations of .env files by offering features like automatic synchronization with cloud platforms (Vercel, Railway, Netlify), Kubernetes operator support, audit logging, automatic rotation, and webhook integrations. The platform supports both CLI and web UI workflows, allows personal environment overrides, and works offline with encrypted cached secrets. It integrates with deployment platforms natively or through custom webhooks for platforms like Dockploy.

  12. 12
    Article
    Avatar of cloudflareCloudflare·22w

    Code Orange: Fail Small — Our resilience plan following recent incidents

    Cloudflare declared "Code Orange: Fail Small" following two major outages in November and December 2025. Both incidents were caused by instantaneous global deployment of configuration changes that broke the network. The resilience plan focuses on three areas: implementing controlled rollouts for configuration changes (similar to existing software deployment processes), reviewing and improving failure modes across all systems to handle errors gracefully, and fixing break glass procedures to remove circular dependencies. The goal is to ensure configuration changes pass through testing gates before global deployment, preventing single changes from taking down the entire network.

  13. 13
    Video
    Avatar of continuousdeliveryContinuous Delivery·23w

    We Tried Trunk-Based Development... The Results Were Shocking.

    A real-world case study from MFT Energy demonstrates how a team successfully adopted trunk-based development by committing directly to main with no branches. The team made ~2,500 commits (90% under 200 lines) while building a power trading bidding service under tight deadlines. Results showed main remained deployable (9/10 score), high quality (8.5/10), excellent DORA metrics, and strong team preference (8.5/10 would continue). Success came from small batches, fast feedback, and low transaction costs. However, non-blocking code reviews scored poorly (6/10, -7 NPS) due to lack of prioritization and unclear purpose. The team found trunk-based development worked well even without mandatory TDD or pair programming, proving that small increments with fast feedback create quality and stability.

  14. 14
    Article
    Avatar of doDigitalOcean·22w

    Speed Up Your JavaScript Apps: Native Bun Support is Now Available on App Platform

    DigitalOcean App Platform now supports Bun natively, allowing developers to deploy Bun applications directly from code repositories without configuration files. The platform uses Cloud Native Buildpacks to automatically detect, build, and deploy Bun apps. Key features include zero-configuration deployment, automatic runtime detection via bun.lock files, and seamless Next.js support. Developers can migrate existing Node.js apps by simply replacing package-lock.json with bun.lock. The platform supports three deployment workflows: Cloud Native Buildpacks, Dockerfiles, and pre-built images.

See all CI/CD archives