Jenkins Git Plugin not pulling latest changes before building job

Question

I am working with Jenkins CI and am trying to properly configure my jobs to use git.

I have the git plugin installed and configured for one of my jobs. When I build the job, I expect it to pull the latest changes for the branch I specify and then continue with the rest of the build process (e.g., unit tests, etc.).

When I look at the console output, I see

> git fetch --tags --progress ssh://gerrit@git-dev/Util +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/some_branch^{commit}
Checking out Revision <latest_SHA1> (origin/some_branch)
 > git config core.sparsecheckout
 > git checkout -f <latest_SHA1>
 > git rev-list <latest_SHA1>

I see that the plugin fetches and checks out the proper commit hash, but when the tests run it seems as though the repo wasn't updated at all. If I go into the repository in Jenkins, I see there that the latest changes were never pulled.

Shouldn't it pull before it tries to build?

I have git 1.8.5 installed on my Jenkins machine, which is a recommended version. https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin

After checking other similar sounding questions on SO, their answers weren't helpful for my problem.

score 51 · Answer 1 · answered Aug 12 '16 at 03:27

51

Relates me to scenario where workspace wasn't getting cleaned-up, used:

Source Code Management--> Additional Behaviours --> Clean after checkout
Other option is to use Workspace Cleanup Plugin

answered Aug 12 '16 at 03:27

Abhijeet

8,561
5
70
76

This is actually the correct way to do it. So I am wondering why this answer is not the selected one. – mhristache Oct 04 '16 at 16:05
1

This option is available on 2.6. – Abhijeet Aug 11 '17 at 03:55
3

This is in 'Build triggers' > 'Pipeline' > 'Additional Behaviours' for me – Cyral Feb 23 '18 at 01:21
I've been trying to solve this issue for 2 days. This made it work. I have a features branch `feature/xx` that Jenkins kept getting old commits instead of the latest one. – Shafiq al-Shaar Apr 26 '19 at 18:02
1

It will remove all untracked/ignored files too. Is there a way to only reset tracked files? – Mostafa Lavaei May 16 '20 at 01:21
if we wipe out the workspace at the begin of a new build, Jenkins is still providing the **"Changes"** built into? – Heinz Jul 18 '23 at 13:13

score 11 · Accepted Answer · answered Dec 30 '14 at 18:46

11

I believe Jenkins pulls the changes and builds in it's own tmp directory. So, your repository directory isn't getting updated although Jenkins is properly building the new code in it's own sandbox.

My solution to this has been to add a "git pull" step in my build process like so:

When a new commit is delivered to my GitHub repo:
1. Build my project

If successful, perform the following post-build steps:
1. Execute Shell:

cd /your/repo/directory/
git pull

You can obviously modify the "git pull" command to do whatever you need to do if a 'pull' doesn't work for you.

answered Dec 30 '14 at 18:46

bpgriner

381
6
14

Thank you, that got me on the right track. What ended up working for me was: git pull -s recursive -X theirs origin myBranch – HRVHackers May 16 '16 at 07:06
See also solution from Abhijeet. – hiaclibe Apr 12 '18 at 08:16
Where did you include the git pull in the jenkins configurations ? I am confused please help me out. – alphaguy Jul 30 '19 at 11:10
For me (in a scripted pipeline case) the workaround was to add "checkout scm" call, without that the workspace and the "Recent Changes" were not updated. The drawback seems to be the workspace cleaning which is run by default in this case (as I see from the log). Just pulling seems to be not implemented yet, I found a ticket about this problem: https://issues.jenkins.io/browse/JENKINS-52916. – Alexander Samoylov Jun 05 '21 at 11:41

score 6 · Answer 3 · answered Nov 21 '19 at 11:00

6

For folks using Jenkins pipeline with git plugin, use Wipe Out repository & force clone under Additional Behaviours of SCM section.

answered Nov 21 '19 at 11:00

Krishna Gupta

1,219
11
12

score 3 · Answer 4 · answered Mar 29 '17 at 02:12

3

I know the question is old, but there is another way to do this. In the Build Environment section, select "Delete workspace before build starts"

See the screenshot below,

This will actually clean the workspace every time and hence you will get the updated code.

answered Mar 29 '17 at 02:12

Harish Talanki

866
13
27

This requires the Workspace Cleanup Plugin - https://plugins.jenkins.io/ws-cleanup/. – trebor Oct 09 '20 at 17:37

score 2 · Answer 5 · answered Apr 12 '18 at 10:01

2

Try to insert your branch path with this format:

refs/remotes/<remoteRepoName>/<branchName>

Tracks/checks out the specified branch.
E.g. refs/remotes/origin/master

answered Apr 12 '18 at 10:01

Francesco Santagati

146
3

score 1 · Answer 6 · edited Dec 20 '22 at 16:24

1

Simply tick the check box in the image:

This Tab saved me the Head aches

edited Dec 20 '22 at 16:24

AJPerez

3,435
10
61
91

answered Jun 12 '19 at 13:44

MassiveConfusion

25
10

This requires the Workspace Cleanup Plugin - https://plugins.jenkins.io/ws-cleanup/. – trebor Oct 09 '20 at 17:34

Jenkins Git Plugin not pulling latest changes before building job

6 Answers6