Azure DevOps throws error: pathspec 'master' did not match any file(s) known to git

Question

We have about 100 running azure-devop pipelines with all the same azure-pipeline.yaml. In all pipelines, we are calling get checkout $(Build.SourceBranchName). In one of the repositories we get the error message:

error: pathspec 'master' did not match any file(s) known to git

On our local machines checking out the master branch does not make any problems. When pushing to any other branch, it is not working as well. E.g. when using dev branch:

error: pathspec 'dev' did not match any file(s) known to git

I can't see any differences. What I tried:

Create everything from scratch
Check whether HEAD ref is equal to master (origin/master)
Creating new branches and push them (e.g. origin/dev) is not working as well
Switching branches does not help

Any other ideas?

What is the result when using git branch? Have you tried the answers from the similar thread: [error: pathspec '...' did not match any file(s) known to git](https://stackoverflow.com/questions/5989592/git-cannot-checkout-branch-error-pathspec-did-not-match-any-files-kn) E.g. `git remote update git fetch git checkout --track origin/` — Minxin Yu - MSFT, Sep 22 '22 at 08:59

score 3 · Accepted Answer · answered May 03 '23 at 01:06

I stumbled across this same issue recently where exactly the same pipeline script was working on an existing project, but not a new one I was setting up. It turns out that the default behaviour of the checkout step changed in September 2022 but any pre-existing pipelines would retain the old behaviour.

To get the pre-September 2022 behaviour back you need to change from this:

steps:
- checkout: self
  persistCredentials: true

to this:

steps:
- checkout: self
  fetchDepth: 0
  fetchTags: true
  persistCredentials: true

Once you've done that you'll be able to access your repo's branches and tags. e.g.

steps:
- checkout: self
  fetchDepth: 0
  fetchTags: true
  persistCredentials: true

- script: |
    git config --global user.email 'ci@example.com'
    git config --global user.name 'AzDO Pipeline'
    git checkout $(Build.SourceBranchName)
  displayName: 'Set up git'

- script: |
    pip install bump2version
    bump2version --verbose ${{ parameters.RELEASE_TYPE }}
  displayName: 'Bump version'

- script: |
    git push origin --tags
    git push origin $(Build.SourceBranchName)
  displayName: 'Push tagged release'

score 1 · Answer 2 · answered Sep 23 '22 at 05:26

1

I would check in that pipeline:

git version
git branch -avv
git switch $(Build.SourceBranchName)

The last command (git switch) would avoid any issue where you checkout a branch which could also be a file name.

answered Sep 23 '22 at 05:26

VonC

1,262,500
529
4,410
5,250

score 1 · Answer 3 · answered Sep 28 '22 at 13:12

I faced the same issue with a newly created repository/project. I have a script with is updating the package version for an angular app. With an repo which was created somewhen in spring. Its checking out code with the real branch name and then creating on one the hash.

 * [new branch]      main       -> origin/main
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin  +67169f67e1151398ee1c86c939f9aea8daad0a46
From https://xxx.visualstudio.com/xxx/_git/xxx
 * branch            67169f67e1151398ee1c86c939f9aea8daad0a46 -> FETCH_HEAD
git checkout --progress --force 67169f67e1151398ee1c86c939f9aea8daad0a46
Note: switching to '67169f67e1151398ee1c86c939f9aea8daad0a46

With that is was able to use $Env:BUILD_SOURCEBRANCH and $Env:BUILD_SOURCEBRANCHNAME

Write-Host "upgrade version"
npm version patch -m "Upgrade to %s ***NO_CI***"
Write-Host "Create temp branch"
git branch tmp
Write-Host "Checkout $SourceBranchPath"
git checkout $Env:BUILD_SOURCEBRANCHNAME -q
Write-Host "Merge tmp to $Env:BUILD_SOURCEBRANCHNAME"
git merge tmp
Write-Host "Update status"
git status
Write-Host "Push changes to origin"
git push origin $Env:BUILD_SOURCEBRANCHNAME -q
Write-Host "Delete tmp branch"
git branch -d tmp -q

But now with the new repo its using the hash at more places.

 * [new ref]         8c41292bd04b87275886d7d012c022273ce83f34 -> origin/8c41292bd04b87275886d7d012c022273ce83f34
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin --depth=1 +8c41292bd04b87275886d7d012c022273ce83f34   
From https://xxx.visualstudio.com/xxx/_git/xxx
 * branch            8c41292bd04b87275886d7d012c022273ce83f34 -> FETCH_HEAD
git checkout --progress --force refs/remotes/origin/8c41292bd04b87275886d7d012c022273ce83f34
Note: switching to 'refs/remotes/origin/8c41292bd04b87275886d7d012c022273ce83f34'

I could get rid of error: pathspec by using $Env:BUILD_SOURCEVERSION for the checkout.

git checkout $Env:BUILD_SOURCEVERSION -q

But neither $Env:BUILD_SOURCEVERSION nor $Env:BUILD_SOURCEBRANCHNAME is working for the final push. There i get:

src refspec main does not match any
error: failed to push some refs to 'xxxx'

score 0 · Answer 4 · answered Sep 29 '22 at 13:44

Meanwhile I got it working.

As it seems to be aware of the current branch its running on, you have to create this branch with
git checkout -b $Env:BUILD_SOURCEBRANCHNAME <- -b

Later on to push back the changes, you have to use
git push origin HEAD:$Env:BUILD_SOURCEBRANCHNAME<- HEAD:

score 0 · Answer 5 · edited Apr 17 '23 at 18:04

0

I had the same problem with a new repo, while the same script worked in an old repo in the same devops project. Not really sure why.

For me the solution was to run git fetch before the checkout.

edited Apr 17 '23 at 18:04

JSON Derulo

9,780
7
39
56

answered Apr 13 '23 at 15:08

Vermaat

1

Azure DevOps throws error: pathspec 'master' did not match any file(s) known to git

5 Answers5