Skip to content

Conversation

MarkEWaite
Copy link
Contributor

[JENKINS-76004] Use git log instead of git whatchanged for changelog

Command line git 2.51.0 has deprecated the "git whatchanged" command and recommends that it be replaced with "git log --raw". Refer to the blog post

Testing done

Interactive testing confirmed that without this change, the changelog that is usually displayed on a freestyle project will silently remain empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

  • Debian 11 (Git 2.30)
  • Debian 12 (Git 2.39)
  • FreeBSD 14 (Git 2.50)
  • Red Hat 8 (Git 2.51, built from source code)
  • Ubuntu 22 (Git 2.34)
  • Ubuntu 24 (Git 2.43)
  • Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

Command line git 2.51.0 has deprecated the "git whatchanged" command and
recommends that it be replaced with "git log --raw".  Refer to the blog
post: https://github.blog/open-source/git/highlights-from-git-2-51/

Testing done:

Interactive testing confirmed that without this change, the changelog
that is usually displayed on a freestyle project will silently remain
empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

* Debian 11 (Git 2.30)
* Debian 12 (Git 2.39)
* FreeBSD 14 (Git 2.50)
* Red Hat 8 (Git 2.51, built from source code)
* Ubuntu 22 (Git 2.34)
* Ubuntu 24 (Git 2.43)
* Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.
@MarkEWaite MarkEWaite added the bug Incorrect or flawed behavior label Aug 19, 2025
@MarkEWaite MarkEWaite requested a review from a team as a code owner August 19, 2025 02:20
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Aug 19, 2025
MarkEWaite added a commit to MarkEWaite/bom that referenced this pull request Aug 19, 2025
https://issues.jenkins.io/browse/JENKINS-76004

Source pull request:

* jenkinsci/git-client-plugin#1326

Verification pull request in the git plugin:

* jenkinsci/git-plugin#1796

Testing done:

Automated tests pass.  Rely on ci.jenkins.io for deeper testing.
@MarkEWaite MarkEWaite removed the documentation Improvements or additions to documentation label Aug 19, 2025
@MarkEWaite MarkEWaite merged commit 9999864 into jenkinsci:master Aug 19, 2025
18 checks passed
@MarkEWaite MarkEWaite deleted the replace-git-whatchanged branch August 19, 2025 11:19
basil pushed a commit to basil/git-client-plugin that referenced this pull request Sep 3, 2025
…enkinsci#1326)

Command line git 2.51.0 has deprecated the "git whatchanged" command and
recommends that it be replaced with "git log --raw".  Refer to the blog
post: https://github.blog/open-source/git/highlights-from-git-2-51/

Testing done:

Interactive testing confirmed that without this change, the changelog
that is usually displayed on a freestyle project will silently remain
empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

* Debian 11 (Git 2.30)
* Debian 12 (Git 2.39)
* FreeBSD 14 (Git 2.50)
* Red Hat 8 (Git 2.51, built from source code)
* Ubuntu 22 (Git 2.34)
* Ubuntu 24 (Git 2.43)
* Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.

(cherry picked from commit 9999864)
MarkEWaite added a commit that referenced this pull request Sep 3, 2025
…1326)

Command line git 2.51.0 has deprecated the "git whatchanged" command and
recommends that it be replaced with "git log --raw".  Refer to the blog
post: https://github.blog/open-source/git/highlights-from-git-2-51/

Testing done:

Interactive testing confirmed that without this change, the changelog
that is usually displayed on a freestyle project will silently remain
empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

* Debian 11 (Git 2.30)
* Debian 12 (Git 2.39)
* FreeBSD 14 (Git 2.50)
* Red Hat 8 (Git 2.51, built from source code)
* Ubuntu 22 (Git 2.34)
* Ubuntu 24 (Git 2.43)
* Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.

(cherry picked from commit 9999864)
MarkEWaite added a commit to MarkEWaite/update-center2 that referenced this pull request Sep 4, 2025
https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is
fixed by backporting the changes from Git Client Plugin 6.3.3

Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb

Git Client Plugin 6.2.1 also includes fixes to support command line
git 2.51.0.  Those changes were originally from pull requests:

* jenkinsci/git-client-plugin#1326
* jenkinsci/git-client-plugin#1327

Fixed by pull request:

* jenkinsci/git-client-plugin#1332

Testing done:

I've run interactive tests with Git Client Plugin 6.2.1 incremental
build and found no issues.
MarkEWaite added a commit to MarkEWaite/git-client-plugin that referenced this pull request Sep 4, 2025
…enkinsci#1326)

Command line git 2.51.0 has deprecated the "git whatchanged" command and
recommends that it be replaced with "git log --raw".  Refer to the blog
post: https://github.blog/open-source/git/highlights-from-git-2-51/

Testing done:

Interactive testing confirmed that without this change, the changelog
that is usually displayed on a freestyle project will silently remain
empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

* Debian 11 (Git 2.30)
* Debian 12 (Git 2.39)
* FreeBSD 14 (Git 2.50)
* Red Hat 8 (Git 2.51, built from source code)
* Ubuntu 22 (Git 2.34)
* Ubuntu 24 (Git 2.43)
* Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.

(cherry picked from commit 9999864)
@MarkEWaite MarkEWaite mentioned this pull request Sep 4, 2025
6 tasks
MarkEWaite added a commit that referenced this pull request Sep 4, 2025
…1326)

Command line git 2.51.0 has deprecated the "git whatchanged" command and
recommends that it be replaced with "git log --raw".  Refer to the blog
post: https://github.blog/open-source/git/highlights-from-git-2-51/

Testing done:

Interactive testing confirmed that without this change, the changelog
that is usually displayed on a freestyle project will silently remain
empty when using command line git 2.51.0.

With this change, the changelog displays as expected.

Automated tests pass on:

* Debian 11 (Git 2.30)
* Debian 12 (Git 2.39)
* FreeBSD 14 (Git 2.50)
* Red Hat 8 (Git 2.51, built from source code)
* Ubuntu 22 (Git 2.34)
* Ubuntu 24 (Git 2.43)
* Windows 11 (Git 2.50.1)

Those test combinations are a wide range of versions of command line git.

(cherry picked from commit 9999864)
MarkEWaite added a commit to MarkEWaite/update-center2 that referenced this pull request Sep 4, 2025
https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is
fixed by backporting the changes from Git Client Plugin 6.3.3

Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb

Git Client Plugin 6.1.4 also includes fixes to support command line
git 2.51.0.  Those changes were originally from pull requests:

* jenkinsci/git-client-plugin#1326
* jenkinsci/git-client-plugin#1327

Fixed by pull request:

* jenkinsci/git-client-plugin#1333

Testing done:

I've run interactive tests with a Git Client Plugin 6.1.4 development
build and found no issues.  Details are described in pull request:

* jenkinsci/git-client-plugin#1333
Kevin-CB pushed a commit to jenkins-infra/update-center2 that referenced this pull request Sep 5, 2025
…#887)

* Mark SECURITY-3590 as also fixed in Git Client Plugin 6.2.1

https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is
fixed by backporting the changes from Git Client Plugin 6.3.3

Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb

Git Client Plugin 6.2.1 also includes fixes to support command line
git 2.51.0.  Those changes were originally from pull requests:

* jenkinsci/git-client-plugin#1326
* jenkinsci/git-client-plugin#1327

Fixed by pull request:

* jenkinsci/git-client-plugin#1332

Testing done:

I've run interactive tests with Git Client Plugin 6.2.1 incremental
build and found no issues.

* Mark SECURITY-3590 as also fixed in Git Client Plugin 6.1.4

https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is
fixed by backporting the changes from Git Client Plugin 6.3.3

Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb

Git Client Plugin 6.1.4 also includes fixes to support command line
git 2.51.0.  Those changes were originally from pull requests:

* jenkinsci/git-client-plugin#1326
* jenkinsci/git-client-plugin#1327

Fixed by pull request:

* jenkinsci/git-client-plugin#1333

Testing done:

I've run interactive tests with a Git Client Plugin 6.1.4 development
build and found no issues.  Details are described in pull request:

* jenkinsci/git-client-plugin#1333
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect or flawed behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant