Published Sep 3, 2019

Episode 211: Continuous Delivery on Windows with Rachel Laycock and Max Lincoln

Explore the intricacies of implementing continuous delivery on Windows with industry experts Rachel Laycock and Max Lincoln, as they delve into the transformative power of open source tools, PowerShell automation, and the necessary cultural shifts and community support required for successful enterprise adoption.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Deployment Obstacles

    Deploying applications on Windows presents unique challenges, particularly in achieving continuous delivery. highlights the difficulty of quickly spinning up machines for testing due to licensing issues and vendor tool limitations 1. Open-source tools like Nuget and Chocolaty have emerged to fill gaps in the Windows ecosystem, but notes that while Microsoft is making strides with tools like PowerShell and OneGet, the process remains complex 2. Testing automation scripts often require PowerShell, which can complicate integration testing, though improvements are underway 3.

    One of the biggest blockers to doing continuous delivery on Windows is the ability to spin up machines and start making changes and testing locally as quickly as possible.

    ---

       

    Cultural Shifts

    Implementing continuous delivery and DevOps on Windows requires significant cultural shifts within teams. emphasizes the importance of integrating DevOps practices throughout the development process, rather than as an afterthought 4. discusses the need for a culture of continuous improvement and adaptability, as software ecosystems are constantly evolving 5. Embracing change and fostering collaboration between developers and operations can lead to more efficient and effective software delivery 6.

    We need to start thinking about how our system works in production, and get out of the mindset of a two-year plan that never changes.

    ---

       

    Infrastructure Automation

    Automating infrastructure on Windows involves navigating various tools and environments. explains that tools like Chef, Puppet, and Ansible are essential for infrastructure automation, allowing operations to be scripted and version-controlled 7. However, the integration of PowerShell and desired state configuration presents challenges, as these tools differ from general-purpose programming languages 7. The introduction of package management tools like OneGet and Chocolaty marks a significant shift for Windows, simplifying the deployment process by providing a more Linux-like package management experience 8.

    Nuget's been around for a while and it's been fairly successful. And recently Microsoft announced OneGet, which is a tool they're building into Windows.

    ---

Related Episodes