Using GitPython in Azure DevOps pipelines causes 'git: 'credential-manager-core' is not a git command

Question

When we use GitPython in Azure DevOps and try to push to a repository, the following message occurs (same repository as cloned by the pipeline):

  stderr: 'git: 'credential-manager-core' is not a git command. See 'git --help'.

Infrastructure: GitHub, Windows build machine (latest)

Since our working-directory is the currently cloned repository, we initialize the repository like this:

import git
repo = git.Repo('.')
# Do some stuff
repo.git.execute('git add --all -- ":!build-infrastructure"')
repo.git.execute(f'git commit -m "{generic_commit_message}"')
repo.git.execute('git push')

So pushing the changes should work with the same credentials, as Azure DevOps used for pulling. Am I missing something?

SOLUTION

The solution is to override the checkout step in the pipeline: https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema#checkout

steps:
  - checkout: self
    submodules: true
    persistCredentials: true

side note : you should be able to call git subcomannds as though they were methods of the repo.git object (link to docs) e.g : repo.git.add('--all', '--', ':!build-infrastructure'), repo.git.commit('-m', generic_commit_message), repo.git.push(), etc ... — LeGEC
– LeGEC, Commented Nov 3, 2020 at 13:12

LeGEC · Accepted Answer · 2020-11-03 13:15:37Z

1

Check what url is used for the remote is registered : repo.git.remote('-v')

It could be that the url is one that wouldn't need credentials when pulling.

I, for one, don't know how the container (or process or whatever) that is started by Azure DevOps is created ; it could well be that the setup is done with one account, then the commands are executed with a different one (or within a container, or ... )

Check how the config is set up : repo.git.config('-l'), if target executable is available from the $PATH ...

You may need to add some step in the setup part of your pipeline (e.g: install said credential manager).

answered Nov 3, 2020 at 13:15

LeGEC

53.4k5 gold badges69 silver badges127 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

BendEg Over a year ago

thanks for you help, the solution was to allow connection persistence in the checkout-step.

BendEg · Accepted Answer · 2020-11-03 21:19:44Z

1

SOLUTION

The solution is to override the checkout step in the pipeline: https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema#checkout

steps:
  - checkout: self
    submodules: true
    persistCredentials: true

answered Nov 3, 2020 at 21:19

BendEg

21.3k17 gold badges69 silver badges135 bronze badges

2 Comments

BendEg Over a year ago

@CeceDong-MSFT I will do this, it's just possible tomorrow.

BendEg Over a year ago

@CeceDong-MSFT Were there any changes in behavior? Last week it still worked without checkout ....

Collectives™ on Stack Overflow

Using GitPython in Azure DevOps pipelines causes 'git: 'credential-manager-core' is not a git command

2 Answers 2

1 Comment

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related