Git is not recognized in Windows gitlab ci

Question

I configured a gitlab runner as explained here: https://docs.gitlab.com/runner/install/windows.html

Unfortunately, when I push to my repository, my pipeline fails:

Running with gitlab-runner 10.5.0 (80b03db9)
  on windows runner 79cb4019
Using Shell executor...
Running on WINSTD-45-13...
'"git"' is not recognized as an internal or external command,
operable program or batch file.
'"git"' is not recognized as an internal or external command,
operable program or batch file.
Cloning repository...
'"git"' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
Checking out b05fd8be as master...
'"git"' is not recognized as an internal or external command,
operable program or batch file.
ERROR: Job failed: exit status 9009

When I open the command line utility as administrator, git is available.

Any idea why git is not recognized whithin the pipeline script?

Is your gitlab-runner running as the User or Administrator? Is Git on the path which the gitlab-runner can access? — Rekovni, Mar 07 '18 at 17:33
@Rekovni gitlab-runner is running as Administrator since I started it from an Administrator elevated command prompt as explained in the doc. Git is in the path (when I type `git` in the command prompt, it display `git` available commands) — Martin Delille, Mar 07 '18 at 18:12

score 9 · Answer 1 · answered Feb 04 '21 at 07:02

9

If you installed git after gitlab-runner you have to restart gitlab-runner service.

answered Feb 04 '21 at 07:02

Yunus Eş

159
1
3

score 6 · Accepted Answer · answered Mar 08 '18 at 10:23

6

I solved the problem myself: my .gitlab-ci.yml script was redefining the PATH environment variable.

answered Mar 08 '18 at 10:23

Martin Delille

11,360
15
65
132

2

If possible, could you add an indication on how you did that ? – Gabriel Devillers Jan 18 '19 at 13:11
I was defining a PATH variable so `git` wasn't in the path anymore. – Martin Delille Jan 19 '19 at 14:04
I meant: what did the line of code look defining the variable looked like inside the .gitlab-ci.yml ? – Gabriel Devillers Jan 19 '19 at 16:40
2

I don't remember well but if you post your `.gitlab-ci.yml` somewhere, I might be able to tell you. – Martin Delille Jan 19 '19 at 21:22
Please check this nice post that helped me achieved this: https://appuals.com/fix-git-is-not-recognized-as-an-internal-or-external-command/ Hope this can help others too – Danie Du Preez Aug 09 '21 at 18:51

score 6 · Answer 3 · answered Feb 22 '19 at 07:22

6

For me it happened that I installed git after I started PowerShell to run gitlab-runner. To fix this you need to restart PowerShell after git is installed and then restart gitlab-runner to get git on your PATH.

answered Feb 22 '19 at 07:22

RamiR

139
2
8

score 1 · Answer 4 · answered Apr 20 '19 at 06:06

1

My runner was installed on an Amazon EC2 instance, and I installed git after I installed the runner. I found restarting the entire EC2 instance fixed it. Restarting the service was not enough.

answered Apr 20 '19 at 06:06

Cobertos

1,953
24
43

Exactly the problem I was experiencing. – Corey P Jul 24 '19 at 02:49

score 1 · Answer 5 · answered Oct 19 '21 at 19:07

I had installed git as a user, so it was installed to that user's AppData folder. Even though I could run git --version fine from an elevated console, GitLab for some reason couldn't run it.

I reinstalled git as Administrator, and then stopped and restarted the GitLab Runner service and now it is working properly.

ovsvolvic · Answer 6 · 2018-10-25T02:31:52.567

0

Installing Git on C:\Git instead of c:\Program Files... fixed this problem for me.

edited Oct 25 '18 at 02:31

answered Oct 24 '18 at 07:29

ovsvolvic

3
1

Git is not recognized in Windows gitlab ci

6 Answers6

Linked