Updating GIT

Hi ​@Egor Skepko 

To add an Access node, we need to install Cloud Apps package

We have to download and install Git Package manually

• The Git client application must be installed on the access node. To download Git, see Git Downloads.

• The Git Large File Storage (LFS) package must be installed on the access node. To download and install Git LFS, see Git Installation.

  The installation directories for both Git and Git LFS software must be included in the system environment variables, and the git executables must be accessible via the command prompt.

• Configure Git LFS for large files. Restores to Azure DevOps may fail for repositories larger than 5 GB because Azure DevOps limits pushes to 5 GB.

Refer:

Add an Access Node for DevOps

​@Syed_S Thank you for your answer, but I would like to know more about the Git version and how to update it if necessary

Hi ​@Egor Skepko,

I was wondering the same but haven’t found any information about the update handling.

For now we are updating Git alongside all other components in our monthly maintenance.

In the future I was thinking about switching to a linux access node and maybe doing automatic updates by the package manager.

Either way I would say regular updates should be the way to go especially when doing backups of cloud environments where dependencies on newer versions may become relevant faster.

​@Marcel_RE How do you update it?

​@Egor Skepko There is a command for it “git update-git-for-windows” but you could just use the installer from the website as well.

​@Marcel_RE i am getting next error:

>git update-git-for-windows
11:13:35.341768 exec-cmd.c:243          trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
11:13:35.358768 git.c:750               trace: exec: git-update-git-for-windows
11:13:35.359768 run-command.c:657       trace: run_command: git-update-git-for-windows
11:13:35.435767 exec-cmd.c:243          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
11:13:35.437768 git.c:463               trace: built-in: git config --get http.proxy
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_REVOCATION_OFFLINE (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

​@Egor Skepko the error you got seems to be caused by a certificate error.

Do you have self-signed certificates in use for your proxy? You need to check the revocation server in your certificate and test connectivity.

The error is somewhat self explanatory.