git job weirdness (in Changes)

[David Balazic]

Hi!

I have set up a job in Jenkins v2.387.2 with sources from git and a maven build step.

Last time I committed and pushed two changes into the repo. (one push after both commits)
The Jenkins job detected the change and started a build.

Issues:
- the changes page in Jenkins ( /view/foo/job/my_job/changes ) shows only the second change (the commit message and the author).
Clicking the "detail" link opens /view/foo/job/my_job/4/changes#1234_the_hash where again only the second commit is mentioned.
The files on disk (in the workspace) have the correct content (from both commits).

- on the above details/summary page, there is a list of many files from the repo/working tree with the plus icon prepended
It seems almost every file in the repo (in the branch I checked out) is listed.
This is the same for a previous build too, which was also triggered by SCM change and has one file actually changed.
And the build before that.
This job has 4 builds, and the 3 after the initial build all have this issue of all files being listed, instead only the changed ones.

- on the details/summary page, the "changed" files listed are in black, slightly bold font, but when hovering the mouse over each , that line turns blue and underlined (similar to links), clicking on it has no effect.

Questions:
- why are not both changes (or in general: all changes since previous build) listed?
- why are all files listed, not just the changed ones?
- why the blue underlined text?


Regards,
Lep pozdrav,
David Balažic

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Any opinions expressed are mine and do not necessarily represent the opinions of the Company. Emails are susceptible to interference. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited and may be unlawful. If you have received this message in error, do not open any attachments but please notify the Endava Service Desk on (+44 (0)870 423 0187), and delete this message from your system. The sender accepts no responsibility for information, errors or omissions in this email, or for its use or misuse, or for any act committed or omitted in connection with this communication. If in doubt, please verify the authenticity of the contents with the sender. Please rely on your own virus checkers as no responsibility is taken by the sender for any damage rising out of any bug or virus infection.

Endava plc is a company registered in England under company number 5722669 whose registered office is at 125 Old Broad Street, London, EC2N 1AR, United Kingdom. Endava plc is the Endava group holding company and does not provide any services to clients. Each of Endava plc and its subsidiaries is a separate legal entity and has no liability for another such entity's acts or omissions.

[David Balazic]

I created a new job with the same settings, except:
- the original job (with the issues) had GIT settings to ave disk space, ase described in the thread "git plugin, use --single-branch option to save disk space?" on this list on may 26 2023
- the new job had default GIT options

With the new job, the second issue (all files listed as added) is not present.
So it is a bug in git-client with the nondefault options?

For the record, the different settings in the old job regarding git are:

- Advanced / "Refspec" is not blank (as per default), but: +refs/heads/my_branch:refs/remotes/origin/ my_branch
- "Additional Behaviours" has an "Advanced clone behaviours" item with values:
"Honor refspec on initial clone" enabled
"Shallow clone" enabled

The third issue (file list look) is still present in the new job, while the first (changes list) was not tested as only one commit was done between latest en previous build.

Regards,
David

[Mark Waite]

On Tuesday, July 4, 2023 at 3:09:57 AM UTC-6 David Balazic wrote:

I created a new job with the same settings, except:
- the original job (with the issues) had GIT settings to ave disk space, ase described in the thread "git plugin, use --single-branch option to save disk space?" on this list on may 26 2023
- the new job had default GIT options

With the new job, the second issue (all files listed as added) is not present.
So it is a bug in git-client with the nondefault options?

For the record, the different settings in the old job regarding git are:

- Advanced / "Refspec" is not blank (as per default), but: +refs/heads/my_branch:refs/remotes/origin/ my_branch
- "Additional Behaviours" has an "Advanced clone behaviours" item with values:
"Honor refspec on initial clone" enabled
"Shallow clone" enabled

Shallow clone causes git to request only the depth of commits specified.  Changelog history is computed from the history in the local copy of the repository.  If the history in the  local copy of the repository   is shallow, then it is entirely possible that the history does not exist in that local copy.

[David Balazic]

> Shallow clone causes git to request only the depth of commits specified.  Changelog history is computed from the history in the local copy of the repository.  If the history in the  local copy of the repository   is shallow, then it is entirely possible that the history does not exist in that local copy.

 

Thanks, in between I created another project, that was the same as the original (with the history issue), but without the "Shallow clone" option.

Now the changed file list is as expected, "correct". Only listing the actually changed versions between commits.

 

Regards,

David Balažic

Lead engineer                                                                         Endava

 

From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> On Behalf Of Mark Waite
Sent: Wednesday, 5 July 2023 02:51
To: Jenkins Users <jenkins...@googlegroups.com>
Subject: Re: git job weirdness (in Changes)

 

CAUTION - EXTERNAL EMAIL

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bc75a2c6-5ca8-40dd-9ea4-e8d0edd9d13an%40googlegroups.com.