Check that your git repository actually contains a commit with SHA1
faaf2c4ff254904ca0692a69270b9d342cd8a637 .

If it does, then check that the repository which Jenkins is using actually
contains a commit with SHA1 faaf2c4ff254904ca0692a69270b9d342cd8a637.

Assure that you are not using "shallow clone" in the Jenkins repository,
since a shallow clone may not include the SHA1 you're trying to use.


On Mon, Jul 14, 2014 at 7:01 AM, sai ram <[email protected]> wrote:

> Please help me out with this error,
>
> Command "git read-tree -mu HEAD" returned status code 128:
> stdout:
> stderr: fatal: Not a valid object name HEAD
>
> .
> .
> FATAL: Could not checkout null with start point 
> faaf2c4ff254904ca0692a69270b9d342cd8a637hudson.plugins.git.GitException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>:
>  Could not checkout null with start point 
> faaf2c4ff254904ca0692a69270b9d342cd8a637
>
> .
> .
> Caused by: hudson.plugins.git.GitException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>:
>  Command "git checkout -f faaf2c4ff254904ca0692a69270b9d342cd8a637" returned 
> status code 128:
> stdout:
> stderr: error: Sparse checkout leaves no entry on working directory
>
> .
>
>
>
> *Kind Regards, *
> *Sairam *
> 9884699987 | Skype - vjsairam
>
>
> On Mon, Jul 14, 2014 at 6:28 PM, Mark Waite <[email protected]>
> wrote:
>
>> Yes, it is.  You'll need a git version which supports sparse checkout,
>> and a recent version of git-client-plugin and a recent version of
>> git-plugin.
>>
>> Once you have those pre-requisites, then you click the "Add" button in
>> "Additional Behaviours" and select "Sparse Checkout paths".  We use it very
>> often.  It works well for us.
>>
>> Mark Waite
>>
>>
>> On Mon, Jul 14, 2014 at 6:49 AM, sai ram <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> I want to checkout a particular folder from GIT repo. Please let me know
>>> if this is possible in the latest GIT version.
>>>
>>> Thanks,
>>> *Sairam *
>>>
>>>  --
>>> 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 [email protected].
>>> 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 [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to