Best of CI/CD — January 2026

  1. 1
    Video
    Avatar of codeheadCodeHead·20w

    The Best Way To Learn DevOps in 2026

    Learning DevOps effectively means understanding it as a mindset for reliably moving code to production, not just a collection of tools. Start with Linux fundamentals (processes, networking, system commands) before diving into containers and orchestration. Follow a single application through its entire lifecycle: write it, containerize it, deploy it, break it intentionally, and observe what happens. Implement CI/CD pipelines for consistency, learn cloud infrastructure as code with tools like Terraform, and master observability through logs, metrics, and traces. The key is choosing the simplest architecture that works and only adding complexity when it solves real problems, not to pad a resume.

  2. 2
    Article
    Avatar of mg8wu8viudnhg6nah9thkMehedi Hasan Jim·17w

    Web Development Is More Than Just Frontend and Backend

    Deploying a real web project involves more than just writing frontend and backend code. The deployment process introduces additional complexities like domain management, hosting configuration, and server setup that beginners often don't anticipate when learning web development.

  3. 3
    Article
    Avatar of planetpythonPlanet Python·16w

    The missing 66% of your skillset

    Senior developers need more than just programming language expertise. The ecosystem around Python—including dependency management (uv), Git workflows, testing (pytest), quality control (Ruff, type checkers), CI/CD automation (GitHub Actions), deployment (Docker, Cloud), and CLI proficiency (Makefiles)—comprises roughly two-thirds of professional skillset. Mastering these tools differentiates engineers from scripters and helps developers escape tutorial hell.

  4. 4
    Article
    Avatar of spaceliftSpacelift·20w

    Top 13 Open-Source Automation Tools for 2025

    A curated list of 13 open-source automation tools for DevOps and infrastructure teams in 2025, covering infrastructure as code (Spacelift Intent, OpenTofu, Pulumi), configuration management (Ansible, Puppet, Chef, Salt, CFEngine, Rudder), CI/CD (Jenkins), GitOps (Argo CD), monitoring (Prometheus), and workflow orchestration (Apache Airflow). Each tool is described with key features, licensing, and use cases, along with a comparison table highlighting execution models, configuration approaches, and strengths to help teams choose the right tool for their automation needs.

  5. 5
    Article
    Avatar of octopusdeployOctopusDeploy·19w

    What's new in Argo CD 3.2?

    Argo CD v3.2 GA release introduces significant improvements across multiple areas: UI enhancements including hydration status on app tiles and sortable columns, ApplicationSet controller performance upgrades with better concurrency and error reporting, new health checks for DatadogMetric resources, server-side diff support for more accurate resource comparison, and Hydrator upgrades with custom commit messages and automatic .gitattributes generation. These changes improve usability, observability, and reliability for teams running GitOps at scale.

  6. 6
    Article
    Avatar of planetpythonPlanet Python·16w

    7 Software Engineering Fixes To Advance As A Developer

    Developers often get stuck in "Tutorial Hell" despite knowing syntax and solving code challenges. Seven key engineering shifts can help break this pattern: finishing projects instead of abandoning them, learning the full ecosystem beyond just coding (Docker, Git, Testing, CI/CD), getting feedback instead of coding in isolation, and adopting better debugging practices like the 20-Minute Rule. The focus is on shipping real projects rather than accumulating unfinished courses and repositories.

  7. 7
    Article
    Avatar of salesforceengSalesforce Engineering·16w

    Automating Global Rollback for 1.5 Trillion Requests in 10 Minutes

    Salesforce Edge team reduced global rollback time from 8-12 hours to 10 minutes by implementing a blue-green deployment architecture on Kubernetes. The solution maintains two fully scaled deployments simultaneously, with custom autoscaling logic that evaluates CPU across both fleets to ensure capacity parity. Traffic cutover is automated through service label updates combined with explicit TCP connection draining via mutual TLS, enabling rapid recovery while preserving four-nines availability for a platform handling 1.5 trillion monthly requests and 23 petabytes of traffic across 21+ global points of presence.

  8. 8
    Article
    Avatar of rustRust·17w

    crates.io: development update

    crates.io has added several new features over the past six months, including a Security tab displaying RustSec advisories, expanded Trusted Publishing support for GitLab CI/CD with enforcement options, source lines of code metrics on crate pages, and publication timestamps in the index. The team is also migrating the frontend to Svelte with TypeScript. Additional improvements include filtered download statistics to exclude bots, encrypted GitHub tokens, Fastly CDN integration serving 1.6 PB monthly, and various performance optimizations.

  9. 9
    Article
    Avatar of softwaretestingmagazineSoftware Testing Magazine·16w

    Threat Modeling Meets Agents: Security-Focused AI Agents for Hardening CI/CD Pipelines

    AI agents are evolving from passive LLMs to autonomous systems that can actively secure CI/CD pipelines through threat modeling and self-healing capabilities. However, they introduce new security risks including indirect prompt injection, excessive privileges, and non-deterministic failures. Organizations can harden their pipelines through sandboxed runners, policy-as-code enforcement, human-in-the-loop workflows for high-impact actions, zero trust principles, and layered security defenses across user, LLM, agent, and orchestration layers. A risk-based threat modeling approach helps determine when autonomous action is safe versus requiring human intervention.

  10. 10
    Article
    Avatar of dotnet.NET Blog·19w

    How We Synchronize .NET’s Virtual Monorepo

    The .NET team built a Virtual Monolithic Repository (VMR) that aggregates source code from dozens of standalone repositories into a single git repository for unified builds. The VMR uses a custom two-way synchronization algorithm based on git patches to keep changes flowing between product repositories and the monorepo. The synchronization evolved through three stages: tarball-based Source Build, read-only VMR-lite with one-way sync, and finally a writable VMR with bidirectional flow. The team encountered challenges with conflicting changes, branch lifecycle mismatches, and metadata corruption, ultimately settling on a rebase-based approach that handles conflicts interactively. This infrastructure now powers .NET SDK builds starting from .NET 10 Preview 4.

  11. 11
    Video
    Avatar of techworldwithnanaTechWorld with Nana·18w

    3 Git Workflows Every Developer Should Know (And When to Use Each)

    Git workflows have evolved significantly over the past decade to match modern deployment practices. Git Flow, once the industry standard, uses multiple long-lived branches (main, develop, feature, release, hotfix) and works well for versioned software like mobile apps but adds overhead for continuous delivery. GitHub Flow simplifies this with a single main branch that's always deployable, making it ideal for web applications with frequent deployments. Trunk-based development represents the current best practice for high-performing teams, where developers commit directly to main (or use very short-lived branches) and rely on feature flags, extensive automated testing, and CI/CD pipelines to maintain stability. The evolution reflects improvements in tooling—automated testing, CI/CD, and feature management—that make faster integration possible. Teams often use hybrid approaches, and the right choice depends on your product type, team maturity, test coverage, and deployment frequency.

See all CI/CD archives