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@XXXXX:XXXXXX.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-use...@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.
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
--
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-use...@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.
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 <samuel...@gmail.com> 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+unsubscribe@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 view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEWHEKGn%3Da3%2BGuYZ2MLG8%3D38XzA19GqoTjkJuoYdvc%2BKw%40mail.gmail.com.To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
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
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+unsubscribe@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.
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+unsubscribe@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.