Thank you for looking into this as well! [?]
I will try to recreate your solution.
Thanks again,
John M.
On Wed, Jun 25, 2014 at 1:43 PM, lochrann wrote:
> Hi everybody.
>
> John, I've started reading Jenkins: The Definitive Guide today (I'm a
> Jenkins newbie too) and I've had the very same
Hi everybody.
John, I've started reading Jenkins: The Definitive Guide today (I'm a
Jenkins newbie too) and I've had the very same problem as you.
It's been driving me mad all day long.. Stuck at page 24 - ho la la.
I thought that it was because my Git directory was not at the default place
(G:\
It seems that even though there is a field for the passphrase when I add
the credentials, I have not been able to get the git plugin, ver. 2.2.1,
under Windows 7 to work.
Looks like the next step is to try a public/private key pair that does not
have a passphrase.
On Monday, May 26, 2014 12:5
Alternately, couldn't you generate a private key which does not require a
passphrase and use that instead?
There is at least one bug logged against the git plugin or the git client
plugin that declares it does not support private keys which require a
passphrase.
Refer to https://issues.jenkins-ci
So, more troubleshooting...
I am able to successfully run the following command, using Git Bash, from
the directory that contains my cloned repository.
git.exe fetch --tags --progress
g...@github.com:jmeloro/game-of-life.git
+refs/heads/*:refs/remotes/origin/*
The "catch" is that I am prompted f
> That's just the default. You can configure the service to run as
different user.
Also, would I need to re-create the public/private keys while logged in as
that user?
On Monday, May 26, 2014 5:38:43 AM UTC-4, Daniel Beck wrote:
>
>
> On 26.05.2014, at 02:49, john@gmail.com wrote:
>
> >
That's just the default. You can configure the service to run as different
user.
Okay, how would I do that?
On Monday, May 26, 2014 5:38:43 AM UTC-4, Daniel Beck wrote:
>
>
> On 26.05.2014, at 02:49, john@gmail.com wrote:
>
> > I'm attempting to run Jenkins as a Windows Service, so Jenki
On 26.05.2014, at 02:49, john.mel...@gmail.com wrote:
> I'm attempting to run Jenkins as a Windows Service, so Jenkins is running
> under the Local System Account
That's just the default. You can configure the service to run as different user.
--
You received this message because you are subs
Thank you for the reply.
However, I still need some clarification.
I'm attempting to run Jenkins as a Windows Service, so Jenkins is running
under the Local System Account. So, I am not sure what to use for the
username?
However, when I set up the build job, under the Source Code Management
But are you selecting a credential who's username is git and who's private
key is the key you want Jenkins to access with?
Until you select that credential you will - correctly - see the warning.
If you can't see the credentials drop down then upgrade the git plugin to
at least the 2.x
On Sunday
I've tinkered around some more.
I've copied the private key to the directory where the local system account
is running because on my Windows 7 box I've read that as a service Jenkins
runs under the local system account.
I still do not have the configuration correct. However, I am able to get
pas
Okay, I re-attempting to configure my Jenkins correctly.
Here is where I am coming off the rails:
- When I leave out the "git@" in the SCM URL in the Source Code
Management section, I immediately get the following error:
- "Failed to connect to repository : Command "git.exe ls-rem
You should enter the username as git and not put the git@ in the scm url.
What is happening is that github expects that the username for your key
will *always* be "git". When you specify a username in an ssh key, the git
plugin then replaces the git@ with your username... so despite the fact
that
I tried the Credentials Plugin, but could not get it to work either.
I am out of ideas and am giving up. I've tried for two weeks and am no
closer now than when I started.
I've un-installed Jenkins and deleted my GitHub account.
Signing off and moving on...
On Sun, May 11, 2014 at 9:58 AM, M
Thank You for the prompt response!
I've been struggling with this, off and on, for a couple of weeks now and
am very grateful for any guidance.
So, with that in mind, and in the hopes I can get my installation correct,
I'm starting with a completely clean install. I've removed the old
instanc
I think git plugin use of the credentials plugin is even newer than the
credentials plugin. The first commit reference to credentials in the
git-client-plugin is from 2013, long after the publication date of the book.
I believe the author of "Jenkins - The Definitive Guide" is preparing
revisions
On 11.05.2014, at 15:58, Mark Waite wrote:
> I believe that "Jenkins the Definitive Guide" was published before the
> Credentials plugin was used by the git plugin.
The Credentials plugin 1.0 was released over two years ago in early 2012.
The book was published in 2011, around the time of 1.4
You will probably have a better chance of success if you update your
credentials plugin to the latest version, register your private key in the
"Manage Jenkins", "Manage Credentials" section, then use that registered
credential with your job. That has the benefit that the private key is
managed by
18 matches
Mail list logo
