fixes
>>> it.
>>>
>>> Thanks Mark!!!
>>>
>>> On Monday, 21 October 2019 15:34:16 UTC+13, Patrick van der Velde wrote:
>>>>
>>>> Hi
>>>>
>>>> Our setup
>>>>
>>>> Server:
>>>
ick van der Velde wrote:
>>>
>>> Hi
>>>
>>> Our setup
>>>
>>> Server:
>>> - Jenkins 2.190.1
>>> - Ubuntu 16.04.5
>>>
>>> Agent
>>> - Jenkins swarm slave
>>> - Windows 2016
>>&g
;
>> Our setup
>>
>> Server:
>> - Jenkins 2.190.1
>> - Ubuntu 16.04.5
>>
>> Agent
>> - Jenkins swarm slave
>> - Windows 2016
>>
>> Source control:
>> - GIT on TFS2018
>>
>> When running with git-client plugin 2.8.6 we get
kins swarm slave
> - Windows 2016
>
> Source control:
> - GIT on TFS2018
>
> When running with git-client plugin 2.8.6 we get the following error in
> the build log
>
> Running as SYSTEM
> [EnvInject] - Loading node environment variables.
> Building remotely
The two machines I've seen this on have git versions 2.18.0 and 2.7.4. I
will upgrade those. Will that upgrade fix the issue and allow us to migrate
to the latest version of the GIT plugin?
thanks!
On Monday, 21 October 2019 16:44:11 UTC+13, Mark Waite wrote:
>
> Git client plugin 2
Git client plugin 2.8.4 to git client plugin provided only one change, a
fix for SECURITY-1534
<https://jenkins.io/security/advisory/2019-09-12/#SECURITY-1534>. That is
a remote code execution risk from authenticated git commands when using
repository names that look like options to comman
Hi
Our setup
Server:
- Jenkins 2.190.1
- Ubuntu 16.04.5
Agent
- Jenkins swarm slave
- Windows 2016
Source control:
- GIT on TFS2018
When running with git-client plugin 2.8.6 we get the following error in the
build log
Running as SYSTEM
[EnvInject] - Loading node environment
aite
>
> On Friday, January 6, 2017 at 3:19:52 AM UTC-7, Mark Waite wrote:
>>
>> If you choose to help evaluate the pull request, you can download the
>> latest build from my evaluation branch at
>> https://drive.google.com/open?id=0B9GyYWyfT1N5Y1NPS1hnbU13elk . That
elp evaluate the pull request, you can download the
> latest build from my evaluation branch at
> https://drive.google.com/open?id=0B9GyYWyfT1N5Y1NPS1hnbU13elk . That is
> an unreleased build of the git client plugin which includes the Windows
> password escaping change.
>
>
If you choose to help evaluate the pull request, you can download the
latest build from my evaluation branch at
https://drive.google.com/open?id=0B9GyYWyfT1N5Y1NPS1hnbU13elk . That is an
unreleased build of the git client plugin which includes the Windows
password escaping change.
Mark Waite
On
You can't change the Jenkins git client plugin from using ASKPASS to using
.gitcredentials. The plugin does not have selectable password prompting
methods.
It used .gitcredentials in releases prior to 2.0, and switched to ASKPASS
in releases 2.0 and later. That change was made so that subm
I'm trying to upgrade our Jenkins to 2, but coming accross a problem with
git authentication. I've got Git credentials loaded and they currently
work, but when I upgrade the plugin from 1.19.6 to 2.1.0, all jobs that use
Git for SCM fail with the same error message. As soon as I downgrade the
;ll need to downgrade git client plugin back to the previous version.
> The git client plugin upgrade from 1.x to 2.0 introduces a breaking change
> by switching from JGit 3 to JGit 4, and by changing from Java 6 compatible
> to Java 7 compatible and by switching from requiring a minimum of J
You'll need to downgrade git client plugin back to the previous version.
The git client plugin upgrade from 1.x to 2.0 introduces a breaking change
by switching from JGit 3 to JGit 4, and by changing from Java 6 compatible
to Java 7 compatible and by switching from requiring a minimum of Je
Hi,
After upgrading git client plugin from 1.19.6 to 2.0.0 and git plugin from
2.4.4 to 3.0.0, I got the following error
Caused by: java.lang.NoSuchMethodError:
org.eclipse.jgit.revwalk.RevWalk.release()V 3.0.0 => 2.
well enough for you, you can try other ways
to help.
Some of the ways you might assist the Jenkins git-client-plugin and the
git-plugin projects include:
- Help other users on the Jenkins users mailing list, specifically with
git client and git plugin questions
- Compile and experiment with
Hi,
I am new to open source contribution. I like to contribute Jenkins
git-client-plugin-master project. But I don't understand from where to
start.
So I need your help.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubs
://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?a=b . I
don't know the long term solution, but that was worked every time I've
needed that page.
Mark Waite
On Sun, Jun 26, 2016 at 11:32 AM Ashish Yadav
wrote:
> This page is not showing any version information. Getting ‘blank pag
This page is not showing any version information. Getting 'blank page'.
https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and s
Nice, thank you!
Terry
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christopher Orr
Sent: Wednesday, June 01, 2016 7:07 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Git Client Plugin wiki page missing data?
Hi there,
On 01 Jun 2016, at
Hi there,
> On 01 Jun 2016, at 18:53, Dunnigan, Terrence J
> wrote:
> Does anyone know why the Git Client Plugin wiki page is missing most of its
> data?
>
> Both of these URLs appear to point to the same page, and both appear to be
> missing everything save the Plu
Does anyone know why the Git Client Plugin wiki page is missing most of its
data?
Both of these URLs appear to point to the same page, and both appear to be
missing everything save the Plugin Information table.
https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin
https://wiki.jenkins
Am Mittwoch, 13. April 2016 19:03:37 UTC+2 schrieb Daniel Beck:
>
>
> On 13.04.2016, at 18:30, Daniel Beck >
> wrote:
>
> > Cache weirdness, I think:
> > https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?foo
> >
> > Not sure how to fix t
//wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin
> <https://www.google.com/url?q=https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FGit%2BClient%2BPlugin&sa=D&sntz=1&usg=AFQjCNEtP6VEBlzt3T-dhFj0ewPndeTFNw>
>
> I am not able to view any version history. Did the p
This page is coming up 'blank' for me.
https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin
I am not able to view any version history. Did the page get moved?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To u
Thanks!
On Wed, Apr 13, 2016 at 11:03 AM Daniel Beck wrote:
>
> On 13.04.2016, at 18:30, Daniel Beck wrote:
>
> > Cache weirdness, I think:
> > https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?foo
> >
> > Not sure how to fix though, I'll ask T
On 13.04.2016, at 18:30, Daniel Beck wrote:
> Cache weirdness, I think:
> https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?foo
>
> Not sure how to fix though, I'll ask Tyler.
It's fixed now.
--
You received this message because you are subscribed to the G
On 13.04.2016, at 17:42, Mark Waite wrote:
> It appears that the git client plugin wiki page has been superseded by a new
> page from Steve Cohen. The history of
> https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin shows only one
> version, rather than the many ve
It appears that the git client plugin wiki page has been superseded by a
new page from Steve Cohen. The history of
https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin shows only
one version, rather than the many versions which should exist for that .
Is there a way to delete or revert
onday, February 8, 2016 at 3:01 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>"
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: git plugin, git client plugin and git
If you enabled JGit from the Jenkins global configuratio
difference in my project
configuration page.
Here's the default:
[image: Default-Git-executable.JPG]
Here's the JGit case:
[image: JGit-Git-executable.JPG]
Mark Waite
On Mon, Feb 8, 2016 at 1:38 PM Ashish Yadav
wrote:
> Thanks for the clarification. How/where do I see the option for t
Thanks for the clarification. How/where do I see the option for the git client
plugin to see if it is using the command line git or jgit?
From: Mark Waite mailto:mark.earl.wa...@gmail.com>>
Reply-To:
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>&q
,
remembering timeout values, etc.
The git client plugin provides a git SCM abstraction and allows the user to
select one of two implementations, either command line git, or the pure
Java JGit implementation. It is called by the git plugin (and by other
plugins which need git functionality). The git
client plugin?
Also, why do I need both the git and git client plugin? Why not just the git
client plugin?
--
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
nticating http proxy. The code is still in the git client plugin to
> handle that case.
> https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1324
>
>
> I don't have an authenticating http proxy avail
Have you identified what changed that caused failure?
Some of the things you might try include:
- Backup your installation in case your experiments cause damage
Clear a few plugin directories (so that they can be recreated)
- Move the git client plugin directory (plugins/git-client) to a
Hi All
We tried starting up Jenkins but we get the following error:
org.jvnet.hudson.reactor.ReactorException:
java.lang.NoClassDefFoundError:
hudson/plugins/git/GitLockFailedException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(
I'm not aware of anyone else reporting an issue using git through an
authenticating http proxy. The code is still in the git client plugin to
handle that case.
https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L132
Jenkins : 1.580.2
Git plugin : 2.3.5
Git client plugin : 1.17.1
> /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /usr/bin/git config remote.origin.url http://.../repo.git # timeout=10
Fetching upstream changes from http://.../re
java". "first-parent" logic was
implemented subsequently with
commit#: 777c306e433e7de58702a3fd1e45512a47c0d33a*
Please find below the comment referred to extra builds getting triggered.
https://github.com/jenkinsci/git-client-plugin/commit/340da90500a18866ebba27376c7f1874d673
module commands seems to be 10
>>> minutes still.
>>>
>>> -Allen
>>>
>>>
>>> On Tuesday, September 30, 2014 9:05:15 AM UTC-5, Mark Waite wrote:
>>>>
>>>> I believe the clone timeout value specified in the "Additional
>>&
;> repositories where the initial submodules update would take longer than the
>>>> 10 minute limit and would timeout. I started looking for a solution and
>>>> found that the Git Client Plugin [1] added support for a submodule timeout
>>>> value in version 1.9
>> repositories where the initial submodules update would take longer than the
>> 10 minute limit and would timeout. I started looking for a solution and
>> found that the Git Client Plugin [1] added support for a submodule timeout
>> value in version 1.9.0 [2]. Looking
l that we have been using for years for running
>>> all of our build jobs. Recently we ran into an issue with one of our git
>>> repositories where the initial submodules update would take longer than the
>>> 10 minute limit and would timeout. I started looking for a solu
g for years for running
> all of our build jobs. Recently we ran into an issue with one of our git
> repositories where the initial submodules update would take longer than the
> 10 minute limit and would timeout. I started looking for a solution and
> found that the Git Client Plugi
found that the Git Client Plugin [1] added support for a submodule timeout
value in version 1.9.0 [2]. Looking at the code change [3], it looks like
this should add a timeout field in the submodule options section of the
configuration.
Based upon this, I updated Jenkins and all plugins
Hi all,
We discovered a subtle bug yesterday with the Git Client plugin and its
use of jgit (even if you're using the default command-line git
implementation).
I just noticed that this bug was probably fixed today by a pull request,
but it's worth letting Jenkins users know
nigan, Terrence J
mailto:terrence.j.dunni...@boeing.com>> wrote:
Hi all,
I've run into an issue where the latest git plugin / git client plugins time
out. It pulls down the files in .git\objects\pack and elsewhere, but nothing
beyond the .git folder.
Here's my setup:
Jenkins serv
nutes (due to the size of the repository
>>>>> and
>>>>> the limitation in msys git that it cannot transfer more than about 1
>>>>> MB/second using ssh).
>>>>>
>>>>> The next release of the git plugin (after 2.0.1) adds a ti
s git that it cannot transfer more than about 1
>>>> MB/second using ssh).
>>>>
>>>> The next release of the git plugin (after 2.0.1) adds a timeout field
>>>> to the job configuration so that users with large repositories (like you
>>>> an
the testing, you could
>>> compile the latest git plugin and install it on a separate Jenkins instance
>>> for testing.
>>>
>>> Refer to https://issues.jenkins-ci.org/browse/JENKINS-20445.
>>>
>>> Refer to https://github.com/jenkinsci/git-plugin/p
ting.
>>
>> Refer to https://issues.jenkins-ci.org/browse/JENKINS-20445.
>>
>> Refer to https://github.com/jenkinsci/git-plugin/pull/197 for the
>> changes to git-plugin.
>>
>> Refer to https://github.com/jenkinsci/git-client-plugin/pull/92 for the
>> changes to
g, you could
> compile the latest git plugin and install it on a separate Jenkins instance
> for testing.
>
> Refer to https://issues.jenkins-ci.org/browse/JENKINS-20445.
>
> Refer to https://github.com/jenkinsci/git-plugin/pull/197 for the changes
> to git-plugin.
>
> Refe
/pull/197 for the changes
to git-plugin.
Refer to https://github.com/jenkinsci/git-client-plugin/pull/92 for the
changes to git-client-plugin, already available in 1.6.2
You should probably avoid the JGit implementation when using large
repositories. The recent JGit versions no longer hang when
've run into an issue where the latest git plugin / git client plugins
>> time out. It pulls down the files in .git\objects\pack and elsewhere, but
>> nothing beyond the .git folder.
>>
>>
>>
>> Here's my setup:
>>
>>
>>
>> Jenki
I ran into the same problem today for the first time. I am using Git plugin
1.5.0 (still scared to jump to 2.0) and Git Client Plugin 1.6.1. I don't
use plink, but rather the ssh included with msysgit 1.8.5. My Windows
slaves are connected using JNLP.
I desperately need some way to control
ent plugins
> time out. It pulls down the files in .git\objects\pack and elsewhere, but
> nothing beyond the .git folder.
>
>
>
> Here's my setup:
>
>
>
> Jenkins server:
>
> Jenkins LTS 1.532.1 running on a Windows 7 PC
>
> Jenkins GIT client plugin 1
Hi all,
I've run into an issue where the latest git plugin / git client plugins time
out. It pulls down the files in .git\objects\pack and elsewhere, but nothing
beyond the .git folder.
Here's my setup:
Jenkins server:
Jenkins LTS 1.532.1 running on a Windows 7 PC
Jenkins GIT cli
edentials in URL should still work anyway. Is there a stacktrace using
> this URL-with-credentials as git scm url ?
>
>
> 2013/10/29 schujk >
>
>> First time working with a mac...I feel I'm missing something obvious.
>>
>> -Installed Jenkins (1.509), applied
obvious.
>
> -Installed Jenkins (1.509), applied latest Jenkins GIT plugin and Jenkins
> GIT client plugin
> -Git configuration complete in Jenkins
> -Our git repo is out at an http location, confirmed access to this url.
> -New jenkins job, select git as scm, provide git URL which in
First time working with a mac...I feel I'm missing something obvious.
-Installed Jenkins (1.509), applied latest Jenkins GIT plugin and Jenkins
GIT client plugin
-Git configuration complete in Jenkins
-Our git repo is out at an http location, confirmed access to this url.
-New jenkin
Thanks, upgrading both together seems to work ok.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 20 February 2013 11:49
To: jenkinsci-users@googlegroups.com
Subject: Re: Git client plugin 1.0.2 broken
git plugin 1.2.0 was
> Upgrading the Git client plugin from 1.0.1 to 1.0.2 results in an "ERROR"
> text with a stack trace on the config page of a job that uses Git (see
> below). Rolling back solves the problem.
> Matthew
>
> Status Code: 500
> Exception: java.lang.IllegalAcce
Upgrading the Git client plugin from 1.0.1 to 1.0.2 results in an "ERROR" text
with a stack trace on the config page of a job that uses Git (see below).
Rolling back solves the problem.
Matthew
Status Code: 500
Exception: java.lang.IllegalAccessError: tried to acc
64 matches
Mail list logo
