On Sun, Sep 29, 2019 at 6:47 PM 'Henry Xu' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Hi, thanks for your suggestion. I downgrade the git from 2.21.0 to 2.17.1
> (the version I used on the old machine) and anything work fine. I am
> wondering why the git version may cause
Hi, thanks for your suggestion. I downgrade the git from 2.21.0 to 2.17.1
(the version I used on the old machine) and anything work fine. I am
wondering why the git version may cause issue of this kind.
On Monday, September 30, 2019 at 8:01:52 AM UTC+8, Mark Waite wrote:
>
>
>
> On Sun, Sep 29,
On Sun, Sep 29, 2019 at 5:12 PM Henry Xu wrote:
> I guess I have same issue. And it's wired as it works will on a machine I
> provisioned a year ago. Can you kindly provide more detail about how to
> using Global Tool Configuration to fix this problem? Thanks in advance.
>
>
The Jenkins global
I guess I have same issue. And it's wired as it works will on a machine I
provisioned a year ago. Can you kindly provide more detail about how to
using Global Tool Configuration to fix this problem? Thanks in advance.
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
On Wed, Jun 12, 2019 at 9:52 AM Giles wrote:
> Hi Mark.
>
> Correct again:
>
> - Git plugin 3.10.0, now downgraded to 3.9.1
>
Git plugin 3.10.0 is a good choice. Upgrade to it.
> - Git client plugin 3.0.0-rc, now downgraded to 2.7.6
>
>
Git client plugin 3.0.0-rc is a bad choice. Don't
Hi Mark.
Correct again:
- Git plugin 3.10.0, now downgraded to 3.9.1
- Git client plugin 3.0.0-rc, now downgraded to 2.7.6
Deploys do now appear to all be working (this time I waited until we'd done
a fair bit of testing before reporting ...).
I upgraded the above plugins to 4.0.0-rc and
On Tue, Jun 11, 2019 at 4:53 PM Giles wrote:
> Unfortunately, I appear to have gone from the frying pan to the fire. I
> ran one deploy that hadn't worked previously and it did work, and I
> immediately responded with an "it's working" message. And that single
> deploy still works. But
Unfortunately, I appear to have gone from the frying pan to the fire. I
ran one deploy that hadn't worked previously and it did work, and I
immediately responded with an "it's working" message. And that single
deploy still works. But multiple others (all based on the same code, with
only
I'm glad that helped. In the past, we've seen cases where a new version of
ssh surprises the credential integration that is used by the git plugin. I
don't think your case is related to that, but I did see that Git for
Windows 2.22.0 now includes OpenSSH 8.0. I need to add that version into
my
Nailed it in one.
I was sure it was a Jenkins issue ... but I'd upgraded Cygwin at the same
time, and that probably included their version of git. Which yes, is my
default git. I changed "Manage Jenkins" -> "Global Tool Configuration" ->
git to the just-installed "Git for Windows", and ...
Are you quite sure that your configuration did not change in about the same
time as that upgrade?
The log file indicates that you're running command line git as provided by
Cygwin. Is that intentional? Has it always been that way?
I don't test the Jenkins git plugin with Cygwin. I test with
11 matches
Mail list logo