blocks|key|1141619|text|它看起来更像这样(代理的工作目录)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1141620|​|1141621|📷|atomic|offset|length|1141622|1141623|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/d39c4f4d1940b475ca89169ade864b0c.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

It looks more like this(work directory of an Agent):
<a href="https://i.stack.imgur.com/dk1Hk.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dk1Hk.png" alt="enter image description here" /></a>

blocks|key|1141668|text|文档给出了文件夹结构的示例。如果这还不够，那么添加一个运行gci+-rec+-directory+%7C+select-object+fullname或类似程序的gci+-rec+-directory+%7C+select-object+fullname步骤。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1141669|entityMap^0|T|18|27|18|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

The documentation gives you examples of the folder structure. If that's not enough, add a PowerShell step that runs <code>gci -rec -directory | select-object fullname</code> or similar.

blocks|key|1141788|text|您可以使用CMD任务在Microsoft托管的windows代理中调用树命令来获取文件夹结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1141789|我的脚本：|style|BOLD|1141790|echo+"Structure+of+work+folder+of+this+pipeline:"
tree+$(Agent.WorkFolder)\1+/f

echo+"Build.ArtifactStagingDirectory:"+

echo+"$(Build.ArtifactStagingDirectory)"

echo+"Build.BinariesDirectory:"+

echo+"$(Build.BinariesDirectory)"

echo+"Build.SourcesDirectory:"

echo+"$(Build.SourcesDirectory)"|code-block|syntax|javascript|1141791|结果：|1141792|​|1141793|📷|atomic|1141794|1141795|$(Agent.WorkFolder)代表当前代理的工作文件夹，$(Agent.WorkFolder)\1代表当前管道的工作文件夹(通常第一个管道将放在$(Agent.WorkFolder)\1中，第二个$(Agent.WorkFolder)\2.)|CODE|1141796|因此很明显，对于一个管道运行，默认情况下它有四个文件夹:a(工件文件夹)、b(二进制文件夹)、s(源文件夹)和TestResults(测试结果文件夹)。s文件夹是下载源代码文件的地方。对于构建管道：$(Build.SourcesDirectory)、$(Build.Repository.LocalPath)和$(System.DefaultWorkingDirectory)表示相同的文件夹。更多细节请参见预定义变量。|1141797|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/command-line?view=azure-devops&tabs=yaml|1|https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tree|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/cb4454e09b82b9a46fde940eee6d8f79.png|imageAlt|3|https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml^0|5|5|0|Z|3|1|0|0|5|0|0|0|3|0|0|0|1|2|0|0|0|J|W|L|24|L|2U|L|0|24|1|2R|P|3H|T|4B|X|5O|5|3|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]|$A|1L|B|1M|1|1N]]|C|$]]|$1|D|3|E|5|6|7|1O|8|@$A|1P|B|1Q|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1R|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1S|8|@$A|1T|B|1U|F|G]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1V|8|@]|9|@]|C|$]]|$1|Q|3|R|5|S|7|1W|8|@]|9|@$A|1X|B|1Y|1|1Z]]|C|$]]|$1|T|3|P|5|6|7|20|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|21|8|@$A|22|B|23|F|W]|$A|24|B|25|F|W]|$A|26|B|27|F|W]|$A|28|B|29|F|W]]|9|@]|C|$]]|$1|X|3|Y|5|6|7|2A|8|@$A|2B|B|2C|F|W]|$A|2D|B|2E|F|W]|$A|2F|B|2G|F|W]|$A|2H|B|2I|F|W]]|9|@$A|2J|B|2K|1|2L]]|C|$]]|$1|Z|3|-4|5|6|7|2M|8|@]|9|@]|C|$]]]|10|$11|$5|12|13|14|C|$15|16]]|17|$5|12|13|14|C|$15|18]]|19|$5|1A|13|1B|C|$1C|1D|1E|-4]]|1F|$5|12|13|14|C|$15|1G]]]]

You can use <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/command-line?view=azure-devops&amp;tabs=yaml" rel="noreferrer">CMD task</a> to call <a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tree" rel="noreferrer">tree command</a> in Microsoft-Hosted windows agent to get the folder structure.
My script:
<pre><code>echo &quot;Structure of work folder of this pipeline:&quot;
tree $(Agent.WorkFolder)\1 /f

echo &quot;Build.ArtifactStagingDirectory:&quot; 

echo &quot;$(Build.ArtifactStagingDirectory)&quot;

echo &quot;Build.BinariesDirectory:&quot; 

echo &quot;$(Build.BinariesDirectory)&quot;

echo &quot;Build.SourcesDirectory:&quot;

echo &quot;$(Build.SourcesDirectory)&quot;
</code></pre>
The result:
<a href="https://i.stack.imgur.com/0vem3.png" rel="noreferrer"><img src="https://i.stack.imgur.com/0vem3.png" alt="enter image description here" /></a>
<code>$(Agent.WorkFolder)</code> represents the working folder for current agent, <code>$(Agent.WorkFolder)\1</code> represents the working folder for current pipeline.(Normally the first pipeline will be put in <code>$(Agent.WorkFolder)\1</code>, and the second <code>$(Agent.WorkFolder)\2</code>...)
So it's obvious that for one pipeline run, it has four folders by default: a(artifact folder), b(binaries folder), s(source folder) and TestResults(Test results folder). The <code>s</code> folder is where the source code files are downloaded. For build pipeline: <code>$(Build.SourcesDirectory)</code>,<code>$(Build.Repository.LocalPath)</code> and <code>$(System.DefaultWorkingDirectory)</code> represent the same folder. More details see <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&amp;tabs=yaml" rel="noreferrer">predefined variables</a>.

blocks|key|327075|text|另一个选项是将其添加到YAML管道中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327076|-powershell:+Get-ChildItem+-Path+'Insert+root+path'+-recurse|code-block|syntax|javascript|327077|它看起来会像：|327078|Get-ChildItem+-Path+C:\Test\*.txt+-Recurse+-Force

Directory:+C:\Test\Logs\Adirectory

Mode++++++++++++++++LastWriteTime+++++++++Length+Name
----++++++++++++++++-------------+++++++++------+----
-a----++++++++2/12/2019+++++16:16+++++++++++++20+Afile4.txt
-a-h--++++++++2/12/2019+++++15:52+++++++++++++22+hiddenfile.txt
-a----++++++++2/13/2019+++++13:26+++++++++++++20+LogFile4.txt

++++Directory:+C:\Test\Logs\Backup

Mode++++++++++++++++LastWriteTime+++++++++Length+Name
----++++++++++++++++-------------+++++++++------+----
-a----++++++++2/12/2019+++++16:16+++++++++++++20+ATextFile.txt
-a----++++++++2/12/2019+++++15:50+++++++++++++20+LogFile3.txt

++++Directory:+C:\Test\Logs

Mode++++++++++++++++LastWriteTime+++++++++Length+Name
----++++++++++++++++-------------+++++++++------+----
-a----++++++++2/12/2019+++++16:16+++++++++++++20+Afile.txt
-a-h--++++++++2/12/2019+++++15:52+++++++++++++22+hiddenfile.txt
-a----++++++++2/13/2019+++++13:26+++++++++++++20+LogFile1.txt

++++Directory:+C:\Test

Mode++++++++++++++++LastWriteTime+++++++++Length+Name
----++++++++++++++++-------------+++++++++------+----
-a----++++++++2/13/2019+++++08:55+++++++++++++26+anotherfile.txt
-a----++++++++2/12/2019+++++15:40+++++++++118014+Command.txt
-a-h--++++++++2/12/2019+++++15:52+++++++++++++22+hiddenfile.txt
-ar---++++++++2/12/2019+++++14:31+++++++++++++27+ReadOnlyFile.txt|327079|这是如果需要更多信息，请提供关于Get-ChildItem命令的文档。|offset|length|327080|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7&WT.mc_id=AZ-MVP-5004321^0|0|0|0|0|2|X|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Another option is to add this to a YAML pipeline:
<pre><code>-powershell: Get-ChildItem -Path 'Insert root path' -recurse
</code></pre>
It will look something like:
<pre><code>Get-ChildItem -Path C:\Test\*.txt -Recurse -Force

Directory: C:\Test\Logs\Adirectory

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2/12/2019 16:16 20 Afile4.txt
-a-h-- 2/12/2019 15:52 22 hiddenfile.txt
-a---- 2/13/2019 13:26 20 LogFile4.txt

 Directory: C:\Test\Logs\Backup

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2/12/2019 16:16 20 ATextFile.txt
-a---- 2/12/2019 15:50 20 LogFile3.txt

 Directory: C:\Test\Logs

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2/12/2019 16:16 20 Afile.txt
-a-h-- 2/12/2019 15:52 22 hiddenfile.txt
-a---- 2/13/2019 13:26 20 LogFile1.txt

 Directory: C:\Test

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2/13/2019 08:55 26 anotherfile.txt
-a---- 2/12/2019 15:40 118014 Command.txt
-a-h-- 2/12/2019 15:52 22 hiddenfile.txt
-ar--- 2/12/2019 14:31 27 ReadOnlyFile.txt
</code></pre>
Here is <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7&amp;WT.mc_id=AZ-MVP-5004321" rel="noreferrer">documentation on the Get-ChildItem command if you need more information</a>

blocks|key|1141976|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1141977|📷|atomic|offset|length|1141978|1141979|来源：本博客中的用户评论|1141980|请注意，根据您的环境，您的完整路径可能看起来不同。|1141981|例如:您的c:\agent_work\1\a路径可以是Build.StagingDirectory或|style|BOLD|1141982|/home/vsts/work/1/a/|1141983|这是基于Agent.BuildDirectory或Pipeline.Workspace变量的。(c：\agent_work\1或/home/vst/work/1或/a/1或类似的东西)|1141984|更多在蔚蓝的文档中|1141985|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/fb7f863161d69b2e1b44f24e6433632f.png|imageAlt|1|LINK|MUTABLE|url|https://dev.to/shleeen/understanding-the-directory-structure-created-by-azure-devops-tasks-1328|2|https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml^0|0|0|1|0|0|0|3|9|1|0|0|5|H|0|0|K|0|0|0|9|2|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1C|8|@]|9|@$E|1D|F|1E|1|1F]]|A|$]]|$1|G|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1H|8|@]|9|@$E|1I|F|1J|1|1K]]|A|$]]|$1|J|3|K|5|6|7|1L|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1M|8|@$E|1N|F|1O|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1P|8|@$E|1Q|F|1R|N|O]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1S|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1T|8|@]|9|@$E|1U|F|1V|1|1W]]|A|$]]|$1|V|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12|13|-4]]|14|$5|15|Z|16|A|$17|18]]|19|$5|15|Z|16|A|$17|1A]]]]

<a href="https://i.stack.imgur.com/M5qRL.png" rel="noreferrer"><img src="https://i.stack.imgur.com/M5qRL.png" alt="enter image description here" /></a>
source: <a href="https://dev.to/shleeen/understanding-the-directory-structure-created-by-azure-devops-tasks-1328" rel="noreferrer">user comment from this blog</a>
Note that your full path may look different based on your environment.
For example: your Build.StagingDirectory path could be c:\agent_work\1\a
OR 
/home/vsts/work/1/a/
This is based on Agent.BuildDirectory or Pipeline.Workspace variable.(c:\agent_work\1 or /home/vsts/work/1 or /a/1 or something similar)
<a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&amp;tabs=yaml" rel="noreferrer">more in azure docs</a>

blocks|key|324922|text|@LoLance的答案对于Windows代理来说是完美的。对于Linux代理，语法略有不同(反斜杠，并移除/f标志)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|324923|++++-+task:+CmdLine@2
++++++inputs:
++++++++script:+%7C
++++++++++echo+"Structure+of+work+folder+of+this+pipeline:"
++++++++++tree+$(Agent.WorkFolder)/1

++++++++++echo+"Build.ArtifactStagingDirectory:"+
++++++++++echo+"$(Build.ArtifactStagingDirectory)"

++++++++++echo+"Build.BinariesDirectory:"+
++++++++++echo+"$(Build.BinariesDirectory)"

++++++++++echo+"Build.SourcesDirectory:"
++++++++++echo+"$(Build.SourcesDirectory)"|code-block|syntax|javascript|324924|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

@LoLance's answer is perfect for Windows agents. For Linux agents, the syntax is slightly different (reverse the slash, and remove the /f flag):
<pre class="lang-yaml prettyprint-override"><code> - task: CmdLine@2
 inputs:
 script: |
 echo &quot;Structure of work folder of this pipeline:&quot;
 tree $(Agent.WorkFolder)/1

 echo &quot;Build.ArtifactStagingDirectory:&quot; 
 echo &quot;$(Build.ArtifactStagingDirectory)&quot;

 echo &quot;Build.BinariesDirectory:&quot; 
 echo &quot;$(Build.BinariesDirectory)&quot;

 echo &quot;Build.SourcesDirectory:&quot;
 echo &quot;$(Build.SourcesDirectory)&quot;
</code></pre>

I'm struggling to picture the folder structure of azure pipelines. I know there are some implicit directories like:
<ul>
<li>$(System.DefaultWorkingDirectory)</li>
<li>$(Build.ArtifactStagingDirectory)</li>
</ul>
Which are both folders on a specific build agent available from the pool.
Is there a way to view the folder structure and get a better understanding how things are laid out?

Azure Pipelines - Is there a way to view the folder structure?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我很难想象蔚蓝管道的文件夹结构。我知道有一些隐式目录，如：$(System.DefaultWorkingDirectory)$(Build.ArtifactStagingDirectory)这两个文件夹都是来自池的特定生成代理上的文件夹。是否有一种方法可以查看文件夹结构并更好地了解布局情况？

问Azure管道-有办法查看文件夹结构吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Azure管道-有办法查看文件夹结构吗？EN