Should I use PowerShell or Bash for Windows agents?

While PowerShell is native to Windows, many teams prefer Bash for cross-platform consistency. This skill provides the compatibility patterns needed to make Bash work reliably on Windows agents.

Why do Bash scripts fail on Windows Azure DevOps agents?

Failures typically occur because Git Bash on Windows (MINGW) automatically converts Windows-style paths or treats backslashes as escape characters, which breaks directory references in scripts.

How does MSYS_NO_PATHCONV fix pipeline issues?

Setting MSYS_NO_PATHCONV=1 disables the automatic path translation in Git Bash, allowing Windows paths to be passed to tools like dotnet or az CLI exactly as they are.

How can I detect if my script is running on a Windows agent?

You can use the Azure Pipelines variable $(Agent.OS) or shell-specific environment variables like $OSTYPE (which returns 'msys' or 'mingw' on Windows) to apply conditional logic.

Azure DevOps Windows Git Bash Compatibility

Name: Azure DevOps Windows Git Bash Compatibility
Author: JosiahSiegel

byJosiahSiegel

•

Deployment & DevOps

Resolves path conversion and shell compatibility issues for Azure Pipelines running on Windows agents using Git Bash.

This skill provides specialized guidance for navigating the complexities of running Git Bash scripts on Windows-based Azure DevOps agents. It addresses the notorious path conversion challenges where MINGW/MSYS environments mangle Windows file paths, provides strategies for shell detection across different operating systems, and offers proven patterns for cross-platform pipeline scripts. By implementing these best practices, developers can eliminate common 'No such file or directory' errors and ensure their CI/CD workflows remain robust and portable across Windows, Linux, and macOS agents.

Key Features

01Automated path conversion control using MSYS_NO_PATHCONV

02Standardized cross-platform pipeline template patterns

03Manual path translation techniques using cygpath

04Diagnostic scripts for troubleshooting Windows agent failures

05Multi-method shell detection (OSTYPE, uname, and Agent.OS)

067 GitHub stars

Use Cases

01Fixing broken Bash scripts on Windows-based Azure DevOps build agents

02Creating portable pipeline templates that work across Linux and Windows

03Configuring self-hosted Windows agents for optimal Git Bash performance

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add josiahsiegel/claude-plugin-marketplace ado-windows-git-bash-compatibility

For use in Claude.ai and ChatGPT

Download Skill

Key Features

01Automated path conversion control using MSYS_NO_PATHCONV

02Standardized cross-platform pipeline template patterns

03Manual path translation techniques using cygpath

04Diagnostic scripts for troubleshooting Windows agent failures

05Multi-method shell detection (OSTYPE, uname, and Agent.OS)

067 GitHub stars

Use Cases

01Fixing broken Bash scripts on Windows-based Azure DevOps build agents

02Creating portable pipeline templates that work across Linux and Windows

03Configuring self-hosted Windows agents for optimal Git Bash performance

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add josiahsiegel/claude-plugin-marketplace ado-windows-git-bash-compatibility

For use in Claude.ai and ChatGPT

Download Skill