Git – Jenkins Git Plugin not pulling latest changes before building job

gitJenkinspluginspull

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.

Best Answer

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

How do you create a new project/repository?

A git repository is simply a directory containing a special .git directory.

This is different from "centralised" version-control systems (like subversion), where a "repository" is hosted on a remote server, which you checkout into a "working copy" directory. With git, your working copy is the repository.

Simply run git init in the directory which contains the files you wish to track.

For example,

cd ~/code/project001/
git init

This creates a .git (hidden) folder in the current directory.

To make a new project, run git init with an additional argument (the name of the directory to be created):

git init project002

(This is equivalent to: mkdir project002 && cd project002 && git init)

To check if the current current path is within a git repository, simply run git status - if it's not a repository, it will report "fatal: Not a git repository"

You could also list the .git directory, and check it contains files/directories similar to the following:

$ ls .git
HEAD         config       hooks/       objects/
branches/    description  info/        refs/

If for whatever reason you wish to "de-git" a repository (you wish to stop using git to track that project). Simply remove the .git directory at the base level of the repository.

cd ~/code/project001/
rm -rf .git/

Caution: This will destroy all revision history, all your tags, everything git has done. It will not touch the "current" files (the files you can currently see), but previous changes, deleted files and so on will be unrecoverable!

Git – How to resolve git saying “Commit your changes or stash them before you can merge”

You can't merge with local modifications. Git protects you from losing potentially important changes.

You have three options:

Commit the change using
```
git commit -m "My message"
```
Stash it.

Stashing acts as a stack, where you can push changes, and you pop them in reverse order.

To stash, type
```
git stash
```
Do the merge, and then pull the stash:
```
git stash pop
```
Discard the local changes

using git reset --hard
or git checkout -t -f remote/branch

Or: Discard local changes for a specific file

using git checkout filename

Best Answer

Related Solutions

Git for beginners: The definitive practical guide

How do you create a new project/repository?

Git – How to resolve git saying “Commit your changes or stash them before you can merge”

Commit the change using

Stash it.

Discard the local changes

Or: Discard local changes for a specific file

Related Topic