Adding a build step seems like it should work. I don't see a way from the
plugin settings to perform a point in time checkout or even to perform a
checkout of a specific SHA1.
Can you share why you want to take a point in time rather than the tip of a
branch? I'm curious about the use model and if that might be a use model which
would be important to others.
Mark Waite
>________________________________
> From: "anthcourt...@gmail.com" <anthcourt...@gmail.com>
>To: jenkinsci-users@googlegroups.com
>Sent: Friday, January 11, 2013 4:33 PM
>Subject: Git plugin and checking out from a specified point in time
>
>
>Hello all,
>
>
>Does anyone have any pointers on how to configure a job within Jenkins (and
>probably more specifically, the Git plugin), so that the git checkout
>corresponds to a point in time. This point in time will be provided as a
>parameter to the build.
>
>
>Googling around, I have seen many references to using either:
>
>
>$ git checkout 'master@{2012-12-31 23:59'
>
>
>or
>
>
>$ git checkout `git rev-list -n 1 --before="2012-12-31 23:59" master`
>
>
>
>to checkout a point in time revision, but I can't see a clear way in how to
>then configure the jenkins job or the git plugin.
>
>
>Do I need to add a step like this as an execute shell step? Would I still use
>the git plugin to checkout master first? How will it work for subsequent
>builds of the same project?
>
>
>cheers,
>Anth
>
>
