On 26 October 2017 at 00:44, Samuel Mutel <[email protected]> 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 <https://jenkins.xit.rxcorp.com/user/smutel> > [Thu Oct 26 09:38:03 CEST 2017] Starting branch indexing... > > git --version # timeout=10 > > git ls-remote > ssh://[email protected]/CIO/schedular/schedular-frontend.git # > timeout=10 > > git rev-parse --is-inside-work-tree # timeout=10 > Setting origin to > ssh://[email protected]/CIO/schedular/schedular-frontend.git > > git config remote.origin.url > ssh://[email protected]/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://[email protected]/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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/12601f97-7110-4018-b437-dc052a259b88%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/12601f97-7110-4018-b437-dc052a259b88%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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 [email protected]. 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.
