Checkout Part Of A Branch In Azure DevOps Pipelines (GetSources)


Answer :

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.

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

- checkout: none

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

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://your.access.token@path.to.your/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'

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. Get parts of the repo with Azure DevOps Rest API (Git - Items - Get Items Batch).


The other answers work well but I found a different way using potentially newer features of git.

This will fetch to a depth of 1 and show all the files in the root folder plus folder1, folder2 and folder3

        - task: CmdLine@2           inputs:             script: |               git init               git sparse-checkout init --cone               git sparse-checkout set folder1 folder2 folder3               git remote add origin https://<github-username>:%GITHUB_TOKEN%@<your-git-repo>               git fetch --progress --verbose --depth=1 origin               git switch develop           env:             GITHUB_TOKEN: $(GITHUB_TOKEN)

Comments

Post a Comment

Popular posts from this blog

Chemistry - Bond Angles In NH3 And NCl3

Answer : Solution 1: As Tan Yong Boon stated, it is Bent’s Rule with which we can explain the lower bond angle of \ce N F 3 \ce{NF3} \ce NF 3 when compared to \ce N H 3 \ce{NH3} \ce N H 3 . The rule as stated by Henry Bent: Atomic s character concentrates in orbitals directed towards electropositive substituents. Fluorine is more electronegative that hydrogen, and the \ce N − F \ce{N−F} \ce N − F bond would have greater p character than the \ce N − H \ce{N−H} \ce N − H bond. And more s character leads to large bond angles. Thus, the bond angle is greater in \ce N H 3 \ce{NH3} \ce N H 3 than in \ce N F 3 \ce{NF3} \ce NF 3 . Now, consider \ce N C l 3 \ce{NCl3} \ce NCl 3 . Clearly, \ce C l \ce{Cl} \ce Cl atom islarger in size than the central atom, nitrogen. Hence the higher bond angle here is due to the steric crowding caused by \ce C l \ce{Cl} \ce Cl atoms.(More pronounced than the electrongativity of \ce C l \ce{Cl} \ce Cl atom). They repel eachother and hence b...
Read more

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz...
Read more

Change The Font Size Of Visual Studio Solution Explorer

Answer : Go to Tools->Options->Environment->Fonts and Colors In "Show Settings for" chose "Environment Font" In "Font" replace Automatic to for example, Arial and change size. Change the font size of that setting, all Font size in the Explorers (Solution Explorer, Server Explorer and Toolbox) and menus will change. You can set that in Tools, Options.
Read more