git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Patton, Timothy'" <tpatton@crateandbarrel.com>, <git@vger.kernel.org>
Subject: RE: Jenkins Git Plugin
Date: Wed, 8 Oct 2025 13:27:48 -0400	[thread overview]
Message-ID: <01e701dc3878$e11c9510$a355bf30$@nexbridge.com> (raw)
In-Reply-To: <CAMnRnOWm8iV+JNcVReczh79pNX2zwsPcJm2z4a+8Uj3E1xcq5Q@mail.gmail.com>

On October 8, 2025 1:10 PM, Timothy Patton wrote:
>I recently started seeing the following in build console output when pulling global
>shared libraries from Git.  I need to see the change history part of the build being
>performed.  How can I restore the previous behavior of retrieving the changelog
>when the shared libraries are pulled from Git?
>
>Commit message: "updated getChangeset to include 5 history entries"
> > D:\git\bin\git.exe rev-list --no-walk
>d30fad4563120956426e48bdfe1cbdb450bf932d # timeout=10 'git whatchanged'
>is nominated for removal.
>If you still use this command, please add an extra option, '--i-still-use-this', on the
>command line and let us know you still use it by sending an e-mail to
><git@vger.kernel.org>.  Thanks.
>fatal: refusing to run without --i-still-use-this
>ERROR: Unable to retrieve changeset
>hudson.plugins.git.GitException: Error: D:\git\bin\git.exe whatchanged --no-abbrev
>-M "--format=commit %H%ntree %T%nparent %P%nauthor %aN <%aE>
>%ai%ncommitter %cN <%cE> %ci%n%n%w(0,4,4)%B" -n 1024

Please contact the Jenkins GitSCM support group and ask them to fix the plugin to
use git log instead of git whatchanged.

--Randall


      parent reply	other threads:[~2025-10-08 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08 17:10 Jenkins Git Plugin Patton, Timothy
2025-10-08 17:21 ` Kristoffer Haugsbakk
2025-10-08 17:27 ` rsbecker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='01e701dc3878$e11c9510$a355bf30$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=tpatton@crateandbarrel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).