I don't think the plugin is the problem in your case.  If it is, you've
found a glaring failure in a widely used plugin.  It is possible, but seems
unlikely.

The log entries you listed seem to confirm that the plugin performs the
fetch and the checkout of the latest SHA-1.  That is the functional
equivalent of a "git pull".  I suspect there is something else wrong in
your job configuration.

You might try inserting a first build step "git log -n 1" to report the
most recent checkout in the working directory before your actual build
steps begin.

You might try inserting a final build step "git log -n 1" to report the
checkout in the working directory after your build completes.

You might double check that your build script is building from the working
directory, not from some other directory.

You might also describe the platform where you're running the job, any
non-default settings you've used for the git plugin configuration of that
job, and if you are using other plugins which may interact with the git
plugin (like one of the Gerrit plugins).

Thanks,
Mark Waite

On Wed, Sep 10, 2014 at 2:43 PM, polarice <yuteng...@gmail.com> wrote:

> 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. Why is this plugin behaving this way?
>
> *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
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to