咨询Private Agent中_work目录下文件夹编号递增的原因

Hey there! Your two hypotheses are spot-on—both are highly probable reasons for the work directory number incrementing, especially since you’re still new to VSTS. Let’s break down exactly why each scenario triggers this change:

• Enabling build directory cleanup: If you started with the "Clean" option turned off in your build definition, VSTS would reuse the same _work/10/s directory for every subsequent build to save setup time. Once you enable cleanup, though, VSTS creates a fresh numbered directory (in this case /11/s) for each new build to eliminate conflicts from leftover artifacts, logs, or cached files. This is a super common trigger when you start refining your build pipeline to ensure consistency.

• Modifying your build definition: Any meaningful change to your build setup—like adding/removing tasks, switching agent pools, updating repository settings, or even adjusting variable values—can prompt VSTS to spin up a new work directory. The platform does this to isolate builds from different definition versions, so old files from your original setup don’t mess with the updated build process. Even small tweaks can trigger this, since VSTS prioritizes build reliability over reusing directories when there’s any risk of contamination.

Since you’ve only run a handful of builds so far, this number jump is just VSTS doing its job to keep your pipeline clean and consistent as you iterate on your setup. No need to worry about it—this is totally normal behavior for the platform.

原始提问：我们当前使用_work/10/s等路径，此前几次构建均采用该路径，但不知何种原因会导致路径编号升级为/11？我们尚处于使用VSTS初期阶段，因此构建次数较少。我推测原因可能是最初未清理工作目录而现在已开启清理，或是修改构建定义所导致，这两种推测均具有合理性。

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