Re: Multibranch Pipeline - GIT - SSH authentication

[Samuel Mutel]

It works now with Git Plugin 3.6.3. Thanks.

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e042ee8e-61a9-4c84-9da4-2088972a4ff6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Stephen Connolly]

On 26 October 2017 at 10:34, Samuel Mutel  wrote:

> Indexing requires read access to the repository... so that it can, you
> know, see what branches have a Jenkinsfile
> => OK but why the module does not use the SSH key for that operation?
> Is-it a bug?
>

Are you using Jenkins Git Plugin 3.6.1 or 3.6.2? If so, yes it's
JENKINS-47629 and I have a PR to fix... if not, we'll need more details

> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/b56235c8-c402-447a-b385-33425eb4a4d4%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMygwD52Qfc3EW11sORNjFD4%3DAJODEDHDuf9%3DB0XhFCsLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Samuel Mutel]

Indexing requires read access to the repository... so that it can, you 
know, see what branches have a Jenkinsfile
=> OK but why the module does not use the SSH key for that operation? Is-it 
a bug?

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b56235c8-c402-447a-b385-33425eb4a4d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Stephen Connolly]

On 26 October 2017 at 00:44, Samuel Mutel  wrote:

> Hello,
>
> I think I found the explanation of my issue. I setup the private key
> directly on the jenkins home and it works fine.
> All my project are private in GITLAB and the module Multibranch Pipeline
> is not using the private key setup inside the job for the branch indexing.
> The module use the private key after. We can see this in the log below
> (using GIT_SSH to set credentials toto).
> Now the question is : could we setup a private project in GITLAB but
> authorize the branch indexing to public ... ?
>

Indexing requires read access to the repository... so that it can, you
know, see what branches have a Jenkinsfile

If you can figure out a way to keep a repository private but allow public
read access then you are a smarter person than me


>
> Started by user Mutel, Samuel 
> [Thu Oct 26 09:38:03 CEST 2017] Starting branch indexing...
>  > git --version # timeout=10
>  > git ls-remote 
> ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
> timeout=10
>  > git rev-parse --is-inside-work-tree # timeout=10
> Setting origin to 
> ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git
>  > git config remote.origin.url 
> ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
> timeout=10
> Fetching & pruning origin...
> Fetching upstream changes from origin
>  > git --version # timeout=10
> using GIT_SSH to set credentials toto
>  > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
> --prune
> Listing remote references...
>  > git config --get remote.origin.url # timeout=10
> using GIT_SSH to set credentials toto
>  > git ls-remote -h 
> ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
> timeout=10
> Checking branches...
>   Checking branch master
>   ‘Jenkinsfile-test’ found
> Met criteria
> No changes detected: master (still at 
> 055c9f366de388694ac5d9970da8208b8d8ea935)
> Processed 1 branches
> [Thu Oct 26 09:38:08 CEST 2017] Finished branch indexing. Indexing took 5 sec
> Finished: SUCCESS
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/12601f97-7110-4018-b437-dc052a259b88%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzU26niiqKMtZjOvTRv-4Zj8Gk02aD4oaNZgyCeifCJ5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Samuel Mutel]

Hello,

I think I found the explanation of my issue. I setup the private key 
directly on the jenkins home and it works fine.
All my project are private in GITLAB and the module Multibranch Pipeline is 
not using the private key setup inside the job for the branch indexing.
The module use the private key after. We can see this in the log below 
(using GIT_SSH to set credentials toto).
Now the question is : could we setup a private project in GITLAB but 
authorize the branch indexing to public ... ?

Started by user Mutel, Samuel 
[Thu Oct 26 09:38:03 CEST 2017] Starting branch indexing...
 > git --version # timeout=10
 > git ls-remote 
 > ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
 > timeout=10
 > git rev-parse --is-inside-work-tree # timeout=10
Setting origin to 
ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git
 > git config remote.origin.url 
 > ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
 > timeout=10
Fetching & pruning origin...
Fetching upstream changes from origin
 > git --version # timeout=10
using GIT_SSH to set credentials toto
 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
 > --prune
Listing remote references...
 > git config --get remote.origin.url # timeout=10
using GIT_SSH to set credentials toto
 > git ls-remote -h 
 > ssh://g...@git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # 
 > timeout=10
Checking branches...
  Checking branch master
  ‘Jenkinsfile-test’ found
Met criteria
No changes detected: master (still at 055c9f366de388694ac5d9970da8208b8d8ea935)
Processed 1 branches
[Thu Oct 26 09:38:08 CEST 2017] Finished branch indexing. Indexing took 5 sec
Finished: SUCCESS

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/12601f97-7110-4018-b437-dc052a259b88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Stephen Connolly]

If it was a github server, you would need the username in the credentials
to be `git` and not `jenkins` because GitHub only accepts SSH connections
with the username `git`. I wonder if something similar is happening with
gitlab?

On 25 October 2017 at 03:59, Mark Waite  wrote:

> You may need to look more carefully at the configuration of the
> multibranch pipeline job.  If it is using a username/password credential,
> then either the credential named "jenkins" in your configuration is not a
> private key (which it seems to be to me) or there is a location in the job
> which defines an https URL to the repository.
>
> On Wed, Oct 25, 2017 at 4:45 AM Samuel Mutel 
> wrote:
>
>> I tried also to "enter directly" the private key but it does not work.
>> Something curious ... When I parse the log file of the SSH server located
>> on the GITLAB server, I see error message related to a connection with
>> login/password and not related to a connection with ssh key.
>> It's mean that the job is not using ssh key at all.
>>
>> --
>> 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
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/dcc7d24b-7cc5-49e7-9787-
>> dacdc69843cc%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAO49JtEWHEKGn%3Da3%2BGuYZ2MLG8%
> 3D38XzA19GqoTjkJuoYdvc%2BKw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw_7%2BYdSNKSG7nU9h39NiDehD0grzWw207dtv3GPzr6Ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Mark Waite]

You may need to look more carefully at the configuration of the multibranch
pipeline job.  If it is using a username/password credential, then either
the credential named "jenkins" in your configuration is not a private key
(which it seems to be to me) or there is a location in the job which
defines an https URL to the repository.

On Wed, Oct 25, 2017 at 4:45 AM Samuel Mutel  wrote:

> I tried also to "enter directly" the private key but it does not work.
> Something curious ... When I parse the log file of the SSH server located
> on the GITLAB server, I see error message related to a connection with
> login/password and not related to a connection with ssh key.
> It's mean that the job is not using ssh key at all.
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/dcc7d24b-7cc5-49e7-9787-dacdc69843cc%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEWHEKGn%3Da3%2BGuYZ2MLG8%3D38XzA19GqoTjkJuoYdvc%2BKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Samuel Mutel]

I tried also to "enter directly" the private key but it does not work.
Something curious ... When I parse the log file of the SSH server located 
on the GITLAB server, I see error message related to a connection with 
login/password and not related to a connection with ssh key.
It's mean that the job is not using ssh key at all.

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dcc7d24b-7cc5-49e7-9787-dacdc69843cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Mark Waite]

Those settings seem reasonable to me.  I don't see anything in that which 
should be any problem.  If you insert the content of that file in the 
"enter directly" selection, does it behave any differently?  I generally 
use "enter directly" myself, though I know of no reason why the other 
techniques would not work equally as well.

I assume the private key in that file does not require a passphrase, since 
there isn't one in the passphrase field.

Mark Waite

On Wednesday, October 25, 2017 at 1:56:31 AM UTC-6, Samuel Mutel wrote:
>
> Here is my multibranch config:
>
>
> 
>
>
> Here is my credential config:
>
>
>
> 
>
> Started
>
> [Wed Oct 25 09:47:52 CEST 2017] Starting branch indexing...
>
>  > git --version # timeout=10
>
>  > git ls-remote ssh://
> git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # timeout=10
>
> ERROR: [Wed Oct 25 09:48:00 CEST 2017] Could not update folder level 
> actions from source f1c31476-efde-455c-983b-1a3c120cf9a0
>
> hudson.plugins.git.GitException: Command "git ls-remote ssh://
> git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git" returned status 
> code 128:
>
> stdout: 
>
> stderr: 
>
> Permission denied, please try again.
>
> Permission denied, please try again.
>
> Received disconnect from 10.121.1.11 port 22:2: Too many authentication 
> failures
>
> Authentication failed.
>
> fatal: Could not read from remote repository.
>
>
>
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/09c48186-c92d-47b2-adc0-bda1044e3fbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Samuel Mutel]

Here is my multibranch config:




Here is my credential config:




Started

[Wed Oct 25 09:47:52 CEST 2017] Starting branch indexing...

 > git --version # timeout=10

 > git ls-remote 
ssh://git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git # timeout=10

ERROR: [Wed Oct 25 09:48:00 CEST 2017] Could not update folder level 
actions from source f1c31476-efde-455c-983b-1a3c120cf9a0

hudson.plugins.git.GitException: Command "git ls-remote 
ssh://git.xit.rxcorp.com/CIO/schedular/schedular-frontend.git" returned 
status code 128:

stdout: 

stderr: 

Permission denied, please try again.

Permission denied, please try again.

Received disconnect from 10.121.1.11 port 22:2: Too many authentication 
failures

Authentication failed.

fatal: Could not read from remote repository.



-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f1aeb23c-90c6-4562-9681-860d1e13aee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Mark Waite]

Username / password is supported only with http/https protocol.  If you're
using ssh protocol, you'll need to use a private key.

Private key is supported only with ssh protocol.  If you're using http or
https protocol, you'll need to use username / password.

The message "too many authentication failures" may hint that the target
system has "locked you out".

Mark Waite

On Tue, Oct 24, 2017 at 8:53 AM Robert Hales  wrote:

> I use both these methods on jobs. Usually I use the Login/Password on
> https urls. But it definitely works. Not sure how I can give you more
> information to help in your situation. It just seems to be bad ID or PW/ssh
> key.
>
>
> On Tuesday, October 24, 2017 at 8:48:10 AM UTC-6, Samuel Mutel wrote:
>>
>> Hello,
>>
>> I setup a multibranch pipeline job in Jenkins.
>>
>> In branch sources, I used GIT.
>>
>> With this job, for GIT authentication I tried to use credentials stored
>> in Jenkins:
>>   - SSH private key stored in the master
>>   - Login/Password
>>
>> Unfortunately it does not work ...
>>
>> ERROR: [Tue Oct 24 16:15:13 CEST 2017] Could not update folder level actions 
>> from source 61faff97-9161-4212-87c4-399a6b858ae0
>> hudson.plugins.git.GitException: Command "git ls-remote 
>> git@X:XX.git" returned status code 128:
>> stdout:
>> stderr:
>> Permission denied, please try again.
>> Permission denied, please try again.
>> Received disconnect from XX.XX.XX.XX port 22:2: Too many authentication 
>> failures
>> Authentication failed.
>> fatal: Could not read from remote repository.
>>
>>
>> Thanks
>>
>>
>>
>> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8474205d-69d5-458c-9908-1356bbdbf7da%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEK4zo31mO-goQPYPPVvpf0jJ%3DRe9bRruv-pKSUDzyouw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline - GIT - SSH authentication

[Robert Hales]

I use both these methods on jobs. Usually I use the Login/Password on https 
urls. But it definitely works. Not sure how I can give you more information 
to help in your situation. It just seems to be bad ID or PW/ssh key. 

On Tuesday, October 24, 2017 at 8:48:10 AM UTC-6, Samuel Mutel wrote:
>
> Hello,
>
> I setup a multibranch pipeline job in Jenkins.
>
> In branch sources, I used GIT.
>
> With this job, for GIT authentication I tried to use credentials stored in 
> Jenkins:
>   - SSH private key stored in the master
>   - Login/Password
>
> Unfortunately it does not work ...
>
> ERROR: [Tue Oct 24 16:15:13 CEST 2017] Could not update folder level actions 
> from source 61faff97-9161-4212-87c4-399a6b858ae0
> hudson.plugins.git.GitException: Command "git ls-remote git@X:XX.git" 
> returned status code 128:
> stdout: 
> stderr: 
> Permission denied, please try again.
> Permission denied, please try again.
> Received disconnect from XX.XX.XX.XX port 22:2: Too many authentication 
> failures
> Authentication failed.
> fatal: Could not read from remote repository.
>
>
> Thanks
>
>
>
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8474205d-69d5-458c-9908-1356bbdbf7da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.