在Azure DevOps管道(GetSources)中检出分支的一部分 [英] Checkout part of a branch in Azure DevOps Pipelines (GetSources)

问题描述

我组织的devops项目中的存储库包含许多.net解决方案以及一些统一项目.当我运行构建管道时，由于以下几种原因，该管道失败了:

My repository in my organisation's devops project contains a lot of .net solutions and some unity projects as well. When I run my build pipeline, it fails due to several of these:

错误MSB3491:无法将行写入文件"obj \ Release \ path \ to \ file".磁盘上没有足够的空间.

Error MSB3491: Could not write lines to file "obj\Release\path\to\file". There is not enough space on the disk.

我希望管道仅检出和获取成功构建所需的存储库部分.这可能还有助于缩短管道的执行时间，因为它目前还以GB的资源获取了我的整个统一项目，而这需要花费很长的时间.

I would like the pipeline to only checkout and fetch parts of the repository that are required for a successful build. This might also help with execution time of the pipeline since it currently also fetches the whole of my unity projects with gigabytes of resources which takes forever.

我想将我的项目分布在多个存储库中，但是管理员给我的东西不多于我已经拥有的那个.当我将git fetch配置为浅(--depth=1)时，效果会好很多，但是我仍然时不时地收到错误消息.

I would like to spread my projects across multiple repositories but the admin won't give me more than the one I already have. It got a lot better when I configured git fetch as shallow (--depth=1) but I still get the error every now and then.

这是我配置结帐的方式:

This is how I configured the checkout:

steps:
- checkout: self
  clean: true
  # shallow fetch
  fetchDepth: 1
  lfs: false
  submodules: false

使用VSBuild@1任务完成构建.

除了使用多个存储库之外，我无法找到解决问题的有效方法.

I can't find a valid solution to my problem except for using multiple repositories, which is not an option right now.

Shayki Abramczyk的解决方案#1完美运行.这是我的完整实现.

GitSparseCheckout.yml:

parameters:
  access: ''
  repository: ''
  sourcePath: ''

steps:
- checkout: none

- task: CmdLine@2
  inputs:
    script: |
      ECHO ##[command] git init
      git init
      ECHO ##[command] git sparse-checkout: ${{ parameters.sourcePath }}
      git config core.sparsecheckout true
      echo ${{ parameters.sourcePath }} >> .git/info/sparse-checkout
      ECHO ##[command] git remote add origin https://${{ parameters.repository }}
      git remote add origin https://${{ parameters.access }}@${{ parameters.repository }}
      ECHO ##[command] git fetch --progress --verbose --depth=1 origin master
      git fetch --progress --verbose --depth=1 origin master
      ECHO ##[command] git pull --progress --verbose origin master
      git pull --progress --verbose origin master

以这样的方式签出Checkout(必须调整模板路径):

Checkout is called like this (where template path has to be adjusted):

- template: ../steps/GitSparseCheckout.yml
  parameters:
    access: anything:<YOUR_PERSONAL_ACCESS_TOKEN>
    repository: dev.azure.com/organisation/project/_git/repository
    sourcePath: path/to/files/

推荐答案

在Azure DevOps中，您没有选择仅获取部分存储库的选项，但是有一种解决方法: 通过在脚本中手动执行相应的git命令，禁用获取源代码"步骤并仅获取所需的源代码.

In Azure DevOps you don't have option to get only part of the repository, but there is a workaround: Disable the "Get sources" step and get only the source you want by manually executing the according git commands in a script.

要禁用默认的获取来源"，只需在checkout语句中指定none:

To disable the default "Get Sources" just specify none in the checkout statement:

- checkout: none

在管道中添加CMD/PowerShell任务，以使用以下2个选项之一手动获取源:

In the pipeline add a CMD/PowerShell task to get the sources manually with one of the following 2 options:

1..仅使用

1. Get only part of the repo with git sparse-checkout. For example, get only the directories src_1 and src_2 within the test folder (lines starting with REM ### are just the usual batch comments):

- script: |
    REM ### this will create a 'root' directory for your repo and cd into it
    mkdir myRepo
    cd myRepo
    REM ### initialize Git in the current directory
    git init
    REM ### set Git sparsecheckout to TRUE
    git config core.sparsecheckout true
    REM ### write the directories that you want to pull to the .git/info/sparse-checkout file (without the root directory)
    REM ### you can add multiple directories with multiple lines
    echo test/src_1/ >> .git/info/sparse-checkout
    echo test/src_2/ >> .git/info/sparse-checkout
    REM ### fetch the remote repo using your access token
    git remote add -f origin https://[e-mail]/repo
    REM ### pull the files from the source branch of this build, using the build-in Azure DevOps variable for the branch name
    git pull origin $(Build.SourceBranch)
    displayName: 'Get only test/src_1 & test/src_2 directories'

现在，在构建任务中，将myRepo设为工作目录. 必须使用访问令牌来获取远程存储库，因为使用checkout: none会阻止使用您的登录凭据. 在管道的最后，您可能需要添加清除myRepo目录的步骤.

Now in the builds task make myRepo the working directory. Fetching the remote repo using an access token is necessary, since using checkout: none will prevent your login credentials from being used. In the end of the pipeline you may want to add step to clean the myRepo directory.

2..通过

2. Get parts of the repo with Azure DevOps Rest API (Git - Items - Get Items Batch).

这篇关于在Azure DevOps管道(GetSources)中检出分支的一部分的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！