TeamCity新手求助：构建报错Cannot exec: No such file or directory（bzip2相关）

Hey there! Since you're new to TeamCity (only 4 hours in—great progress so far!), let's break down how to fix that bzip2 error you're facing. That "Cannot exec" message almost always means TeamCity can't locate the bzip2 executable when running your build, so we'll focus on getting the tool accessible to your build agent.

Step 1: Verify bzip2 is installed on your build agent machine #

First, make sure bzip2 is actually present on the server running your TeamCity build agent:

• Linux/macOS: Open a terminal and run bzip2 --version. If it returns a version number, it's installed; if not, use your package manager (like sudo apt install bzip2 for Debian/Ubuntu, brew install bzip2 for macOS) to install it.
• Windows: bzip2 isn't included by default, so you can install it via Git Bash (it comes bundled with Git for Windows) or use Chocolatey with choco install bzip2. Once installed, test it in a command prompt with bzip2 --version.

Step 2: Ensure bzip2 is in the build agent's PATH #

TeamCity build agents inherit the system environment variables of the user they run as, but sometimes the PATH doesn't include the directory where bzip2 lives:

• Go to your TeamCity server, navigate to Agents > Select your agent > Agent Parameters > Environment Variables.
• Check if the PATH variable includes the directory containing bzip2. For example:
  • Linux/macOS: Typically /usr/bin
  • Windows: If using Git Bash, it might be C:\Program Files\Git\usr\bin; if using Chocolatey, it's usually C:\Program Files\bzip2\bin
• If the directory isn't in PATH, you can add it either at the system level (restart the build agent after changing) or directly in the TeamCity agent's environment variables (under the Agent Parameters page).

Step 3: Use the absolute path to bzip2 in your build steps #

If adjusting the PATH feels too cumbersome, skip straight to using the full path to the bzip2 executable in your build scripts:

• Linux/macOS: Replace bzip2 with /usr/bin/bzip2
• Windows: Replace bzip2 with C:\Program Files\Git\usr\bin\bzip2.exe (or whatever your actual path is)
  This bypasses the PATH lookup entirely, so TeamCity knows exactly where to find the tool.

Step 4: Check build agent user permissions #

Sometimes the user running the TeamCity build agent doesn't have access to the bzip2 executable or its parent directory:

• Try restarting the build agent with a user account that has administrative privileges (Linux: sudo systemctl restart teamcity-agent, Windows: Run the agent service as an admin user)
• Verify the user can run bzip2 --version in their own terminal/command prompt to confirm access.

Bonus Configuration Tips for Your Personal Build Server #

• Standardize tool installations: Keep all build tools (Node.js, Git, bzip2, etc.) in system default directories to minimize path-related headaches.
• Add a test build step: Create a temporary "Command Line" build step that runs echo $PATH (Linux/macOS) or echo %PATH% (Windows) followed by bzip2 --version. This lets you quickly debug environment issues without running your full build.
• Clean builds after fixes: After adjusting configurations, run a Clean Build in TeamCity (Build > Clean Build) to clear any cached build artifacts that might cause unexpected behavior.

内容的提问来源于stack exchange，提问作者eestein