On Thu, Apr 23, 2020 at 8:37 AM Cardamon wrote:
> Hi
> have you eventually figured it out?
> experiencing the same behavior
> Tnx
>
Command line git generates that message when a sparse checkout is
selected. The Jenkins git plugin ignores the message and continues.
If you'd rather not have tha
Hi
have you eventually figured it out?
experiencing the same behavior
Tnx
> The first build of any Branch or Tag the checkout step outputs one line
> with fatal bad object, for a different git commit hash than the one checked
> out.
>
> Anyone know what the reason for this is?
>
> > git fe
It seems the fatal bad object comes from the checkout of the Shared Library
at the beginning of the pipeline.
Loading library pipeline@master
> git fetch --no-tags --progress --
> ssh://g...@git.company.com/tools/jenkins-pipeline-scripts.git
> +refs/heads/*:refs/remotes/origin/*
Checking o
The first build of any Branch or Tag the checkout step outputs one line
with fatal bad object, for a different git commit hash than the one checked
out.
Anyone know what the reason for this is?
> git fetch --tags --progress --depth=25 --
ssh://g...@git.company.com/apps/app-project.git
+refs/
