Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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"

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

Here is my multibranch config: Here is my credential config:

Re: Multibranch Pipeline - GIT - SSH authentication

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

Re: Multibranch Pipeline - GIT - SSH authentication

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: > >