How to migrate bigger repo to azure devops

2024-05-24T11:32:14.2133333+00:00

Hello,

I am migrating from GIT to Devops. My repo is quite huge and while doing git push I am getting error "HTTP 413 curl 22 the requested url retuned error: 413".

I am using Https to do migration. SOmewhere I saw ssh can solve this issue. but when I tried SSH that also not working

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,878 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Amira Bedhiafi 17,786 Reputation points
    2024-05-25T13:45:02.46+00:00

    Based on this old thread , an 413 error will be returned to the client when the size in a request exceeds the maximum allowed size of the client request body. This size can be configured by the parameter client_max_body_size .

    To configure this setting globally for all Ingress rules, the proxy-body-size value may be set in the NGINX ConfigMap 245. To use custom values in an Ingress rule define these annotation:

    nginx.ingress.kubernetes.io/proxy-body-size: 8m
    

    More links :

    https://stackoverflow.com/questions/41144654/git-error-rpc-failed-http-413-curl-22-the-requested-url-returned-error-413-re

    https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413


  2. Smaran Thoomu 11,370 Reputation points Microsoft Vendor
    2024-05-27T09:04:36.07+00:00

    Hi @Jamesphilip, Sijith (Baker Hughes Contractor)

    Based on your query, it seems that you are facing an issue while migrating a large Git repository to Azure DevOps. The error message "HTTP 413 curl 22 the requested url returned error: 413" indicates that the size of the request exceeds the maximum allowed size of the client request body.

    To resolve this issue, you can try increasing the http.postBuffer size in your Git configuration. You can do this by running the following command in your Git Bash or command prompt:

    git config --global http.postBuffer 524288000
    

    This command sets the http.postBuffer size to 500 MB, which should be sufficient for most large repositories. You can adjust this value as per your requirement.

    If you are still facing issues, you can try using SSH instead of HTTPS for migration. To use SSH, you need to generate an SSH key pair and add the public key to your Azure DevOps account.
    For more information, please refer this article to generate an SSH key pair and add it to your account: https://learn.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page

    I hope this helps. Let me know if you have any further questions.