# continuous-delivery Published articles for continuous-delivery. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Introducing Consort: Test-driven development on a branching database DevFeed: [Introducing Consort: Test-driven development on a branching database]() Original publisher: [Read original article]() Author: Kevin Hartman Published: 2026-09-09T13:41:25Z Content type: article Language: en Sources: [Databricks]() Topics: [Test-driven development](), [Database](), [Integration testing](), [Software Engineering](), [Refactoring](), [Continuous Delivery (CD)](), [Pull Request](), [Reverse Engineering]() Tags: [code](), [continuous-delivery](), [database](), [development](), [integration](), [partners](), [platform](), [postgres](), [pull-request](), [refactoring](), [reverse-engineering](), [software](), [software-development](), [testing]() ### AI overview The article introduces Consort, a workflow for applying test-driven development to a branching database. It argues that copy-on-write branches of a real database can replace mocks, bring integration testing into the inner development loop, and let engineers run destructive tests in isolation. Versioned schema migrations can move with the dependent code, enabling what the article calls Data CD and helping catch production database problems during pull requests and merges. ### Source excerpt For 25 years I built software on the practices I grew up with: Kent Beck's TDD, Martin... ## From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 DevFeed: [From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-03T14:03:46Z Content type: article Language: en Sources: [VMware Blogs]() Topics: [GitOps](), [Platform Engineering](), [CI/CD](), [Automation](), [Cloud](), [Provisioning](), [Tooling]() Tags: [argo-cd](), [automation](), [cloud-infrastructure](), [cloud-native](), [continuous-delivery](), [deployment](), [gitops](), [home-page](), [platform](), [platform-engineering](), [provisioning](), [self-service](), [vcf-9-1](), [vcf-automation](), [vmware](), [vmware-cloud-foundation]() ### AI overview This VMware article announces VCF 9.1.1, which introduces a native GitOps service for VCF Automation Org users in Tech Preview. By integrating Argo CD, the update aims to centralize declarative application delivery, continuous delivery pipelines, and lifecycle management at enterprise scale, reducing manual work and operational friction for platform engineering teams. ### Source excerpt In today's fast-paced digital economy, where AI-driven innovation demands unprecedented agility, IT leaders are tasked with more than just provisioning infrastructure; they are expected to deliver a frictionless, self-service platform that accelerates software delivery. For platform engineers, cloud architects, and IT executives, the goal is to bridge the gap between robust infrastructure and modern application ... Continued The post From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 appeared first on VMware Blogs. ## Harness RT Agents Detect Resilience Risks and Generate Tests for CD Pipelines and Kubernetes Workloads DevFeed: [Harness RT Agents Detect Resilience Risks and Generate Tests for CD Pipelines and Kubernetes Workloads]() Original publisher: [Read original article]() Author: Uma Mukkara Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [Resilience](), [Testing](), [Continuous Delivery (CD)](), [Kubernetes](), [dashboards]() Tags: [agentic](), [agents](), [blog](), [chaos](), [configuration](), [continuous-delivery](), [dashboards](), [deployment](), [experiments](), [infrastructure](), [insights](), [kubernetes](), [load](), [pipelines](), [product](), [resilience](), [services](), [teams](), [testing](), [tests]() ### AI overview Harness announces an update to Resilience Testing called RT Agents. The agents analyze CD pipelines and Kubernetes workloads for resilience risks, recommend the testing needed to confirm those risks, and can generate and run chaos experiments or load tests and interpret the results. ### Source excerpt RT Agents detect resilience risk in your CD pipelines and Kubernetes workloads, then generate and run chaos experiments or load tests to confirm it. | Blog ## Continuous Delivery Excellence with Harness IDP DevFeed: [Continuous Delivery Excellence with Harness IDP]() Original publisher: [Read original article]() Author: Rashmi Hegde Published: 2026-08-21T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Continuous Delivery (CD)](), [internal developer portal](), [CI/CD](), [Platform Engineering](), [Deployment](), [Automation](), [Orchestration](), [Provisioning]() Tags: [automation](), [ci-cd](), [continuous-delivery](), [deployment](), [developer-velocity](), [idp](), [internal-developer-portal](), [orchestration](), [platform-engineering](), [provisioning](), [self-service](), [tooling]() ### AI overview This article explains how Harness Internal Developer Portal can support continuous delivery through self-service workflows, standardized deployment pipelines, and unified service catalogs. It argues that delivery friction often comes from cognitive overhead, unclear prerequisites, fragmented permissions and configuration, and insufficiently discoverable workflows rather than a lack of pipeline capability. ### Source excerpt Achieve continuous delivery excellence using Harness Internal Developer Portal. Streamline deployments, boost velocity, and empower developers. Learn more. | Blog ## Q2 2026 Product Update: Harness Continuous Delivery & GitOps DevFeed: [Q2 2026 Product Update: Harness Continuous Delivery & GitOps]() Original publisher: [Read original article]() Author: Vishal Vishwaroop Published: 2026-08-06T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [CI/CD](), [GitOps](), [Deployment](), [Kubernetes](), [AI Agent](), [Cloud Run]() Tags: [2026](), [agent](), [cloud-run](), [continuous-delivery](), [deployment](), [gitops](), [kubernetes](), [product]() ### AI overview Harness reviews its Q2 2026 product updates, covering 38 enhancements across Continuous Delivery, Verification, and GitOps. The update includes progressive Kubernetes canary rollouts, native AI agent deployments, staged Cloud Run traffic, enhanced verification controls, and GitOps rollback and RBAC improvements. ### Source excerpt Progressive canary rollouts, native AI agent deployments, staged Cloud Run traffic, smarter verification controls, and 12 GitOps improvements -- Q2 2026 in revie | Blog ## Native AI Agent Deployment in Harness Continuous Delivery DevFeed: [Native AI Agent Deployment in Harness Continuous Delivery]() Original publisher: [Read original article]() Author: Akshit Madan Published: 2026-07-21T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [AI Agent](), [Deployment](), [Continuous Delivery (CD)](), [Security](), [Software](), [agent observability]() Tags: [agentic](), [ai](), [ai-agent](), [audit-trail](), [continuous-delivery](), [deployment](), [harness](), [progressive-delivery](), [security]() ### AI overview This Harness article introduces agent deployment in Harness Continuous Delivery, with governed pipelines, native runtime support for platforms including Google's Agent Runtime and Amazon Bedrock AgentCore, progressive delivery, policy controls, and audit trails. It explains deployment as a critical stage of the agent development lifecycle and describes coordinating agents with backend services, database changes, and prompt or model configuration. ### Source excerpt Deploy AI agents with Harness Continuous Delivery using governed pipelines, native runtime support, progressive delivery, and built-in security. | Blog ## How To Set Up a Staging Environment on Heroku in 3 Easy Steps DevFeed: [How To Set Up a Staging Environment on Heroku in 3 Easy Steps]() Original publisher: [Read original article]() Author: Andy Smith Published: 2026-07-16T18:23:58Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Deployment](), [Continuous Delivery (CD)](), [Testing](), [pull-requests](), [Git](), [GitHub]() Tags: [continuous-delivery](), [continuous-deployment](), [deployment](), [engineering](), [github](), [heroku](), [heroku-pipelines](), [how-to](), [pull-requests](), [testing]() ### AI overview A tutorial explains how to create a staging environment on Heroku by separating configuration and databases, grouping applications in Heroku Pipelines, and promoting tested compiled slugs to production. It also covers continuous delivery, disabling automatic deployment during setup, and optional Review Apps for pull requests. ### Source excerpt Moving fast should not mean breaking things for your users. While testing on localhost is a good start, you need a near identical replica of production to catch any bugs before your code goes live. That is where a staging environment comes in. Heroku pipelines handle the infrastructure layout for you, keeping your deployment workflow clean and automated. The post How To Set Up a Staging Environment on Heroku in 3 Easy Steps appeared first on Heroku. ## Building the business case for a secure open source supply chain DevFeed: [Building the business case for a secure open source supply chain]() Original publisher: [Read original article]() Published: 2026-05-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [open-source-security](), [vulnerability management](), [cloud-infrastructure](), [CI/CD](), [distributed-systems](), [container images](), [engineering-culture]() Tags: [chainguard-assemble](), [chainguard-containers](), [chainguard-customers](), [cloud-infrastructure](), [cloud-native](), [compliance](), [container-images](), [continuous-delivery](), [cves](), [dependencies](), [distributed-systems](), [kyndryl](), [kyndryl-open-source](), [open-source](), [productivity](), [resilience](), [secure-open-source](), [software-supply-chain-security](), [supply-chain](), [vulnerabilities]() ### AI overview The article explains how organizations can build a business case for a secure open source supply chain. It describes a shift from framing open source security solely around CVEs, scanner results, and patching toward presenting trusted open source as a driver of productivity, resilience, and delivery speed. It also explains why traditional vulnerability management struggles with continuous delivery, distributed systems, frequently rebuilt container images, changing dependencies, and global cloud infrastructure. ### Source excerpt Learn how Kyndryl reframed open source security as a business driver -- reducing risk, lowering costs, and accelerating developer productivity. ## Agentic code workflows with Nick Tune DevFeed: [Agentic code workflows with Nick Tune]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-03-26T16:01:37Z Content type: article Language: en Sources: [Tech World With Milan Newsletter]() Topics: [agentic-coding](), [ai-coding](), [Claude Code](), [Code quality](), [code reviews](), [Test-driven development](), [Testing](), [Command-line interface](), [Domain-driven design (DDD)](), [migration](), [Requirements](), [Continuous Delivery (CD)]() Tags: [agentic](), [agentic-coding](), [agents](), [ai-coding](), [ai-tools](), [best-practices](), [claude-code](), [cli](), [code-quality](), [code-reviews](), [continuous-delivery](), [domain-driven-design](), [migration](), [requirements]() ### AI overview An interview with Nick Tune about advanced agentic coding workflows. It covers planning requirements, modeling development as a tested state machine, implementing features with Claude Code and guardrails, enforcing architecture rules deterministically, reviewing pull requests, applying TDD, and using custom tooling. ### Source excerpt Most engineers who talk about AI productivity talk in abstractions. ## Breaking the release monolith: How OutSystems platform engineering restored trust in delivery DevFeed: [Breaking the release monolith: How OutSystems platform engineering restored trust in delivery]() Original publisher: [Read original article]() Published: 2026-03-19T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Platform Engineering](), [Cloud Native Ecosystem](), [Continuous Delivery (CD)](), [Microservices](), [Kubernetes]() Tags: [chainguard-assemble](), [chainguard-containers](), [cloud-native](), [continuous-delivery](), [kubernetes](), [microservices](), [outsystems](), [outsystems-pegasus](), [platform-engineering](), [release]() ### AI overview The article describes how OutSystems transformed a slow, synchronized software release process through platform engineering. Its cloud-native OutSystems Developer Cloud used microservices and Kubernetes, but releases still followed an older release-train model. The company's journey included building the Pegasus CD platform and restoring trust in delivery. ### Source excerpt At Chainguard Assemble 2026, Outsystems shared how it transformed its release process through platform engineering. ## Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible DevFeed: [Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible]() Original publisher: [Read original article]() Author: Gil Chaouat Published: 2026-01-26T15:56:34Z Content type: article Language: en Sources: [Codefresh]() Topics: [CI/CD Pipeline](), [CI/CD](), [Automation]() Tags: [ci-cd](), [continuous-delivery](), [cost](), [devops](), [performance](), [pipeline](), [product-and-tools]() ### AI overview The article explains how CI/CD pipeline performance profiling can make pipeline behavior, speed, efficiency, cost, and bottlenecks observable and measurable. It also describes how CI/CD automation reduces deployment time and manual errors while providing faster feedback. ### Source excerpt Modern CI/CD pipelines are no longer just about whether builds succeed, they're about how fast, how efficiently, and at what cost they run. Pipeline Performance Profiling is designed to close this gap by making pipeline behavior observable, measurable, and explainable. The post Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible appeared first on Codefresh. ## Heroku GitHub Enterprise Integration enters closed pilot with GitHub App-based connections DevFeed: [Heroku GitHub Enterprise Integration enters closed pilot with GitHub App-based connections]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2025-12-10T16:00:09Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [CI/CD](), [Continuous Delivery (CD)](), [GitHub]() Tags: [continuous-delivery](), [continuous-integration](), [credentials](), [deployment](), [heroku](), [heroku-enterprise](), [heroku-pipelines](), [integration](), [news](), [security]() ### AI overview Heroku announces a closed pilot of its GitHub Enterprise Integration for Heroku Enterprise customers. The integration uses a dedicated GitHub App-based service identity instead of personal OAuth tokens to connect GitHub Enterprise Server or Cloud with Heroku deployment pipelines. ### Source excerpt We're excited to announce a significant enhancement to how Heroku Enterprise customers connect their deployment pipelines to GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud (GHEC). The new Heroku GitHub Enterprise Integration is now available in a closed pilot, offering a more secure, robust, and permanent connection between your code repositories and your Heroku apps. [...] The post Heroku GitHub Enterprise Integration: Unlocking Full Continuous Delivery for Enterprise Customers appeared first on Heroku. ## 2024 Wrapped: Newsletter, Coaching, Books DevFeed: [2024 Wrapped: Newsletter, Coaching, Books]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2025-01-10T15:58:20Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [engineering-culture](), [CI/CD](), [Microservice](), [Testing](), [Publishing]() Tags: [articles](), [continuous-delivery](), [contribution](), [engineering-culture](), [software-architecture](), [testing]() ### AI overview A 2024 retrospective covering the author's newsletter, coaching, training, video and streaming activity, conference participation, book contribution, and community projects. It reports audience and activity metrics, including 63 Substack posts, 125,000 Substack views, 223 coaching sessions, and increased video watch hours. ### Source excerpt Big wins in 2024: Coaching and Training, Meeting Kent Beck, Dave Farley, Sander Hoogendoorn, Speaking at conferences, Book Contribution, Youtube Channel Success, groCTO ## The fundamentals of iOS at Revolut DevFeed: [The fundamentals of iOS at Revolut]() Original publisher: [Read original article]() Author: Illia Kucheriavyi Published: 2024-05-14T11:41:25Z Content type: tutorial Language: en Sources: [Revolut Engineering]() Topics: [iOS](), [iOS development](), [feature flags](), [Mobile](), [SDKs](), [CI/CD](), [experiments](), [Development](), [Agile](), [Testing](), [releases]() Tags: [agile](), [continuous-delivery](), [continuous-integration](), [development](), [development-process](), [experiments](), [feature-flags](), [fundamentals](), [ios](), [ios-development](), [releases](), [revolut](), [sdks](), [software-engineering](), [testing]() ### AI overview This article describes Revolut's iOS development practices, covering its applications and SDKs, weekly App Store updates, continuous integration and delivery, feature flags, gradual rollouts, rollback procedures, and experimentation with statistical measurement. ### Source excerpt Let's take a look behind the scenes of the iOS development at Revolut, where we strive to provide exceptional financial services and seamless customer experiences for the customers who rely on our iOS apps to manage their financial lives. We believe that it's possible to deliver high-quality software, fast. To achieve this we follow a set of important principles and apply a number of modern agile practices, mainly inspired by XP (eXtreme Programming). Deliver fast Currently, on the iOS platform, we have both applications and SDKs. Here's a list of what's live: Revolut, Revolut <18, Revolut Business, Revolut POS and Revolut Pay SDK. All iOS applications are updated in the App Store on a weekly basis. We operate on the principles of continuous integration and continuous delivery to swiftly deliver new functionality to customers -- as soon as a feature or part of it is ready. We've built our own in-house framework for feature-based releases. According to our process, the Product Owner specifies a feature to be enabled starting from a selected version of the application. Then both the application version and its features are rolled out gradually, starting with a small percentage of our customer base. These two approaches -- feature flagging and gradual version and feature rollout -- enable delivering value to customers with the minimum amount of risk. If anything goes wrong, the flag will be turned off or the older version will be re-submitted as rollback, to remove the problematic change. Moreover, feature flags allow team members to easily switch between different user experiences, compare them, or turn them on and off for testing. We've also developed an in-house experimentation platform that allows teams to experiment with new features and measure their impact using predefined metrics in a statistically significant way. This platform guarantees that experiments are properly set up, and that results are produced using a robust statistical framework. All ideas are teste ## Improved Browser Testing on Heroku with Chrome DevFeed: [Improved Browser Testing on Heroku with Chrome]() Original publisher: [Read original article]() Author: Mars Hall Published: 2024-04-09T22:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Browser Automation](), [Chrome](), [Testing](), [CI/CD](), [Continuous Delivery (CD)]() Tags: [automated](), [browser](), [buildpacks](), [chrome](), [ci](), [continuous-delivery](), [continuous-integration](), [developer-tools](), [engineering](), [heroku](), [security](), [testing](), [tests]() ### AI overview Heroku introduces the Chrome for Testing Heroku Buildpack, a community buildpack designed to improve installation reliability for automated browser testing in Heroku apps. It addresses Chrome and Chromedriver version mismatches by keeping their versions aligned for testing environments. ### Source excerpt For developers and businesses offering a web-based product, automated browser testing is a critical tool to ensure continuous delivery of a reliable service. Developers write browser tests by scripting actions against a real browser, simulating real usage by navigating, selecting, and making assertions about web pages and their document elements. In this post, we introduce [...] The post Improved Browser Testing on Heroku with Chrome appeared first on Heroku. ## The 4 best DevSecOps tools for a secure DevOps workflow DevFeed: [The 4 best DevSecOps tools for a secure DevOps workflow]() Original publisher: [Read original article]() Author: Liran Tal Published: 2024-01-23T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [DevSecOps](), [DevOps](), [Security](), [CI/CD](), [Deployment]() Tags: [article](), [awareness](), [ci-cd](), [continuous-delivery](), [continuous-deployment](), [continuous-integration](), [deployment](), [devops](), [devrel](), [devsecops](), [megawatt](), [monitoring](), [open-source-security](), [security](), [snyk-platform](), [testing]() ### AI overview This article explains DevSecOps as the integration of security into continuous integration, continuous delivery, and continuous deployment workflows. It describes security activities such as scanning, testing, validation, and monitoring across the development lifecycle, and discusses how suitable tools can improve security, feedback, and delivery efficiency. ### Source excerpt Learn how DevSecOps tools integrate security into your DevOps workflow from deployment to production. ## How Continuous Delivery Improves Mobile Developer Productivity DevFeed: [How Continuous Delivery Improves Mobile Developer Productivity]() Original publisher: [Read original article]() Author: Ben Published: 2023-07-07T09:58:55Z Content type: article Language: en Sources: [Novoda]() Topics: [Mobile](), [Continuous Delivery (CD)](), [code productivity](), [Release Management](), [Testing]() Tags: [automated](), [ci-cd](), [continuous-delivery](), [developer-productivity](), [engineering](), [mobile](), [mobile-engineering](), [release-cadence]() ### AI overview This article explains how continuous delivery can improve productivity for mobile development teams. It discusses adapting CI/CD practices to mobile constraints, shortening feedback cycles, automating testing, finding bugs faster, and using weekly or fortnightly release cadences to support continual iteration. ### Source excerpt When properly implemented, continuous delivery practices and processes allow your mobile teams to build and deploy products at a much faster rate by improving developer productivity. We explore how. The post How Continuous Delivery Improves Mobile Developer Productivity appeared first on Novoda. ## Deep Work and Collaboration in Platform- and Enabling-Teams DevFeed: [Deep Work and Collaboration in Platform- and Enabling-Teams]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-04-01T06:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [developer-productivity](), [developer tooling](), [CI/CD](), [Testing](), [Monitoring]() Tags: [article](), [collaboration](), [collaboration-culture-deep-work-employee-happiness-practices-team-topologies-developer-product](), [communication](), [continuous-delivery](), [developer-experience](), [developer-productivity](), [developer-tooling]() ### AI overview An opinion article explains how a developer experience team balanced deep work with the responsiveness required of a platform- and enabling-team. It describes collaboration, developer tooling, delivery pipelines, architecture, infrastructure, continuous delivery, and support for building, testing, deploying, running, and monitoring software, then introduces six mechanisms for protecting focus while handling requests. ### Source excerpt Deep Work and Collaboration in Platform- and Enabling-Teams This is the fourth and last articles of my series about deep work. The first article was about the value of deep work for peak performance. The second article was about seven tips for more deep work for individuals. The third articles was about deep work for teams. ## How Wise bootstraps Spinnaker using ArgoCD DevFeed: [How Wise bootstraps Spinnaker using ArgoCD]() Original publisher: [Read original article]() Author: Nick Platt Published: 2023-02-20T12:24:46Z Content type: tutorial Language: en Sources: [Wise Engineering - Medium]() Topics: [argocd](), [spinnaker](), [CI/CD](), [GitOps](), [Kubernetes](), [Microservice](), [Deployment](), [Helm charts](), [Java]() Tags: [argo-cd](), [argocd](), [ci-cd](), [continuous-delivery](), [deployment](), [gitops](), [helm-charts](), [kubernetes](), [microservices](), [platform](), [spinnaker]() ### AI overview Wise explains how it bootstrapped Spinnaker automatically with ArgoCD instead of using a staging Spinnaker to manage production. The article compares Spinnaker's pipeline-based deployment model with ArgoCD's declarative GitOps reconciliation model and describes using ArgoCD and its App of Apps pattern to manage Spinnaker installations across Kubernetes clusters. ### Source excerpt Spinnaker and ArgoCD logos Deploying your deployment tool In our 2 part series, we discussed the state of our CI/CD systems and wrapped up with our vision for CD at Wise, and why we chose Spinnaker. Here's how we set up Spinnaker from scratch, overcoming the technical challenges of bootstrapping a CD platform. We wanted a hands-off and automated way to bootstrap Spinnaker. When researching across industry peers, one approach was to use a staging instance of Spinnaker to manage your production instance. This method of dual Spinnakers, wasn't viable for Wise, due to security concerns with a staging tool having access to change a production environment. It also meant accepting a potentially manual error prone process when managing your staging setup. Instead, we wanted to achieve a fully automatic installation for both of our Spinnaker environments and settled on using ArgoCD. Spinnaker & ArgoCD Spinnaker consists of around 11 Java microservices, which operates on a centralised deployment model -- push based deployments. It utilises pipelines heavily as its deployment strategy, which can be triggered via various input methods e.g. manual, artefact upload etc. Implementing deployments as pipelines allows engineers to describe a release as a set of steps, with powerful concepts such as canary analysis and quality gates built in. This is attractive for Wise, as use of standardised and reusable templates can enforce end consumers to follow a particular paved road e.g. canary deployments with automatic rollbacks. ArgoCD describes itself as "declarative GitOps for Kubernetes". It comprises fewer golang microservices and can be configured to be either centralised or decentralised. By default, ArgoCD differs by not utilising pipeline based deployments, instead operating via a GitOps reconciliation loop as its source of truth. Whatever is defined in Git, ArgoCD will try to reconcile within the cluster. ArgoCD is Kubernetes native and therefore can't be used for deploying infrast ## Adopting Continuous Delivery: More a culture change than automation of processes DevFeed: [Adopting Continuous Delivery: More a culture change than automation of processes]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-12-04T12:07:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Continuous Delivery (CD)](), [Automation](), [Software]() Tags: [automation](), [burnout](), [continuous-delivery](), [continuous-deployment-software-development-developer-productivity-engineering-excellence-organiz](), [faster](), [ownership]() ### AI overview The article argues that adopting continuous delivery requires a culture and process change, not merely automating manual deployment activities. It recommends understanding existing delivery processes, responsibilities, risks, and safety mechanisms before simplifying or automating them. ### Source excerpt Adopting Continuous Delivery: More a culture change than automation of processes Continuous delivery, the process of automatically delivering changes of a system without human interaction, is one of the most beneficial practices that software teams can adopt. In Accelerate, the authors Nicole Forsgren, Jez Humble and Gene Kim, discovered a strong link between using continuous delivery and organisational performance: Teams that continuously deliver their changes have a stronger sense of ownership, get faster feedback and need to rework their code less. Furthermore, deployments are less stressful and the risk of burnout is reduced. ## Zero to One and Beyond: HackerEarth's journey to Continuous Delivery DevFeed: [Zero to One and Beyond: HackerEarth's journey to Continuous Delivery]() Original publisher: [Read original article]() Published: 2021-08-01T00:00:00Z Content type: article Language: en Sources: [HackerEarth]() Topics: [CI/CD](), [Continuous Delivery (CD)](), [Continuous Deployment (CD)](), [ci](), [Deployment](), [Agile]() Tags: [agile](), [ci](), [ci-cd](), [code](), [continuous-delivery](), [continuous-deployment](), [deployment]() ### AI overview HackerEarth describes its journey from frequent but failure-prone deployments toward continuous delivery and continuous deployment. The article explains how continuous integration, fast feedback near the point of failure, deployable software, and on-demand push-button deployments can improve release cadence and reduce costly production issues. ### Source excerpt "Hey the deployment is broken again. Can you push this change again" "Hey, I merged my changes were merged in the morning. I still don't see them in production yet" "Argh, the static files are not updated. We have to run deployment again" These voices hollared across the hallway and this was followed by a huddle to sort things out. These voices soon grew louder and then we realised: Our Deployment is broken. Epilogue At HackerEarth, we have always been good at embracing bleeding edge technologies. We have always taken pride at doing what is right and acknowledge when something needs a fix. A faster delivery cadence and a quicker release cycle are very important for a startup of our scale. Our deployment related problems threatened our fundament need - "Pace" This prompted us to not just fix what was broken but to introduce a new paradigm to deployment - Continuous Deployment. The key tenets of following agile to push consistent smaller pieces of software frequently to customers and get Feedback. As any growing team, we were at one point struggling with - higher deployment failures or critical issues leaking to production. What followed was our path to redemption Circa 2019, HackerEarth was already doing frequent deployments. We had a process to collect, merge, tag and release code into production. But, this was not enough. As it must be obvious now, our feedback cycle was not close to the point of failure. The Integration happened closer to production and any failure is now expensive to fix. This is where our journey up the CI-CD ladder begun. You're doing continuous delivery when: Your software is deployable throughout its lifecycle Your team prioritises keeping the software deployable over working on new features Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them You can perform push-button deployments of any version of the software to any environment on demand" -- Martin Fowler When it all ## Continuous Deployment for AWS Glue DevFeed: [Continuous Deployment for AWS Glue]() Original publisher: [Read original article]() Author: Mohammed Published: 2020-10-15T15:51:25Z Content type: tutorial Language: en Sources: [Brave New Geek]() Topics: [AWS Glue](), [Continuous Deployment (CD)](), [GitHub Actions](), [Jupyter Notebook](), [Amazon S3]() Tags: [analytics](), [analytics-pipeline](), [aws](), [aws-glue](), [ci-cd](), [continuous-delivery](), [continuous-deployment](), [etl](), [github](), [github-actions](), [jupyter](), [jupyter-notebook](), [s3](), [serverless]() ### AI overview A tutorial for automating continuous deployment of AWS Glue ETL jobs. It uses GitHub Actions to generate a Python script from a Jupyter notebook, copy it to Amazon S3, and update the Glue job to use the new script. ### Source excerpt AWS Glue is a managed service for building ETL (Extract-Transform-Load) jobs. It's a useful tool for implementing analytics pipelines in AWS without having to manage server infrastructure. Jobs are implemented using Apache Spark and, with the help of Development Endpoints, can be built using Jupyter notebooks. This makes it reasonably easy to write ETL processes in an interactive, iterative fashion. Once finished, the Jupyter notebook is converted into a Python script, uploaded to S3, and then run as a Glue job. ## Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes DevFeed: [Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-09-12T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [CI/CD](), [GitLab](), [Homelab](), [Docker](), [Kubernetes](), [Docker Image](), [kubectl](), [rancher](), [Dockerfile](), [nginx](), [React](), [Windows]() Tags: [continuous-delivery](), [continuous-integration](), [developer](), [docker](), [docker-container](), [docker-image](), [gitlab-ci](), [guide](), [homelab](), [kubectl](), [kubernetes](), [nginx](), [rancher](), [react](), [registry](), [self-hosted](), [testing](), [unit-tests](), [windows](), [wsl]() ### AI overview This tutorial explains how to set up a self-hosted development pipeline in a homelab. It covers repository setup, unit testing with a GitLab CI runner, building and publishing a Docker image to a container registry, and deploying the container to a self-hosted Kubernetes cluster with kubectl. ### Source excerpt So you're a software engineer or a developer who wants to self-host your own code in your own homelab? Well this is the tutorial for you! In this step-by-step guide we'll walk through setting up a repo, building and testing our own code (with unit tests) in a self-hosted Gitlab CI runner in our CI pipeline, then we'll build a Docker image and push it up to a container registry, then we'll use... ## Interview for BrowserStack's Breakpoint 2020 Conference DevFeed: [Interview for BrowserStack's Breakpoint 2020 Conference]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2020-07-03T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [Continuous Delivery (CD)](), [Cucumber](), [Open Source]() Tags: [bdd](), [conference](), [continuous-delivery](), [engineering-culture](), [interview](), [open-source](), [qa](), [release-engineering](), [test-automation](), [testing]() ### AI overview This article announces Benjamin Bischoff's BrowserStack interview and talk for the virtual Breakpoint 2020 testing summit. It introduces his work in test automation at trivago and describes the company's technical and procedural changes toward more efficient continuous delivery. ### Source excerpt After 15 years as a game/application developer and trainer, Benjamin decided to make test automation his career. He's currently a Test Automation Engineer in trivago's core QA team. Benj... [Next page]()