git diff in zappbuild not retuning actual difference

[VinothKR24]

Hi, We are running DBB version 3.0.1. In impacts.groovy the git diff command is returning 0 files changed while we do have a 10+ COBOL modules changes between these two hash.

git diff --name-only d2f77e80f94e2ad24a308a72bbb3496a5865c9c9 59a6313a45aca206cd16391794a7567366ddc66d
15:53:22 Number of changed files detected since build build.20250403.113113.031 : 0

In USS the git version we use --> git version 2.14.4_zos_b08

While when i run the exact same git diff command below on VSC terminal i can see list of 10+ COBOL codes i intend to see
git diff --name-only d2f77e80f94e2ad24a308a72bbb3496a5865c9c9 59a6313a45aca206cd16391794a7567366ddc66d

In VSC terminal the git version is git version 2.17.0.windows.1

Any reason what's causing this? is it compatibility of DBB version 3 with git version we use in zos?!

Looking forward hearing on this.

Thanks

[dennis-behm]

@VinothKR24 ,

impacts.groovy is a build script on the very initial samples that had been shipped via the DBB community repository. But, in any case the git diff is outside of the DBB framework, and most likely unrelated to the DBB version.

Can you please verify, if your build workspace contains the git history?

You can for instance use
git log --pretty=format:"%h" -10 to list the abbreviated last 10 hashes:

> git log --pretty=format:"%h" -10 
db9fb09
ca0a8be
7527814
237fa4b
3fb11a0
f4e39b4
746fba0
12b85fe
bfacfd6
fdeee2b

Is there more output you could share with us, such as the build log?

[VinothKR24]

Hi Dennis, thanks for the response. Got it. Yeah just realized from the trace I have added that there was a stream closed error message when it's processing that caused this it looks like. It was happening all day on friday. But today during reruns we don't see the stream closed error message while executing impacts groovy and hence git diff seems to respond back with right differences. Thanks