Jenkins master to slave connection is giving key verification error.
Hi Team, We have set up a Master slave configuration it is giving Error as Host Key Verification Strategy failed and we had the strategy i.e Non Verifying Verification Strategy , but even after that the host are offline. Please suggest what need to be done, once we Comment the KexAlgorithms and MACs these two lines in the SSHD_Config File , the nodes are online, Please give a permanent solution for these ? -- 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/282b391f-6cde-400f-a56d-6d41ac2db654n%40googlegroups.com.
Re: Multibranch Pipeline / Git question -- Use same information as used to retrieve Jenkinsfile
Great. Thank you and Philipp for your fast and helpful replies.
On Friday, July 1, 2016 at 1:16:48 PM UTC-4, Antonio Muñiz wrote:
>
>
> On Fri, Jul 1, 2016 at 5:08 PM, KP >
> wrote:
>
>> Or extend "checkout scm" so that I can use a subdirectory?
>
>
> Try this:
>
> dir('a_subdirectoty') {
> checkout scm
> }
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>
--
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/88f32700-897f-42ea-892d-35c8f34f791a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Multibranch Pipeline / Git question -- Use same information as used to retrieve Jenkinsfile
I am also interested in this, but for a slightly different reason. I want
to checkout into a sub-directory using git. I know that I can do that by
using syntax like:
checkout([$class: 'GitSCM', branches: [[name: '**']],
doGenerateSubmoduleConfigurations: false, extensions: [[$class:
'RelativeTargetDirectory', relativeTargetDir: 'SUBDIR']], submoduleCfg: [],
userRemoteConfigs: [[credentialsId: '', url: 'MYURL']]])
but I need to supply the credentials and url (which I don't want to do in a
committed Jenkinsfile). Can I use the same credentials/url as would be used
in "checkout scm" somehow? Or extend "checkout scm" so that I can use a
subdirectory? Or do I need to set the parameters in the job and use those
instead?
Thanks.
On Tuesday, May 31, 2016 at 11:54:25 AM UTC-4, Antonio Muñiz wrote:
>
> You can use `checkout scm` which will clone the repository at the same
> revision than the previously fetched Jenkinsfile.
>
> On Tue, May 31, 2016 at 5:00 PM, Greg Smith > wrote:
>
>>
>> Hello,
>>
>> I have a question that is probably obvious, but I couldn't seem to find
>> it anywhere. Apologies for my newbie question:
>>
>> If I have a multibranch Pipeline job, does my Jenkinsfile need to do the
>> git extract? Or should that be assumed as part of the retrieval of the
>> Jenkinsfile?
>>
>> For example, lets say I have project "MyProject", with branch "master",
>> with a Jenkins file like this:
>>
>> node() {
>>stage 'Checkout'
>>// git -- Do I need to do the git checkout here??
>>git credentialsId: '1ab8712b-28f4-498e-af0f-433b409675ea', url:
>> 'g...@github.com:smithgcovert/MyProject.git'
>>
>> // build stuff
>> }
>>
>> Now I branch master to "newtestbranch" -- it has the same Jenkinsfile at
>> the top.
>>
>> 1) Do I even need the git extract step? It would seem to be implied by
>> the fact that the Jenkins file was found in that branch... but it seems i
>> do from the testing I've done
>> 2) How can I pass the url and branch into the git step, so that I do not
>> put a path to the repo in the file that is checked in?
>>
>> IE, I want the repo URL, and the branch being built, and the credentials
>> used to do the extract to all be defined by the same url, branch, creds
>> that were used to retrieve the Jenkinsfile. It seems wrong to have any
>> url, branch or credential information in the Jenkinsfile -- is there a way
>> to say "extract the same as used to retrieve the Jenkinsfile"?
>>
>> Thanks,
>> Greg
>>
>> --
>> 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/549e1e95-d6f2-4c40-83b4-b731fdbf2ba6%40googlegroups.com
>>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>
--
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/bfaaa109-7e5d-4add-ae6c-4ed32b4c4e0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Jenkins failed to record SCM polling
Exactly the same issue, but with (old built-in 1.x) CVS plugin. Issue went away after revert tot 1.488. After the lazy loading problem made jenkins unusable, now this... It seems the stability of the jenkins updates is getting very bad lately. 2 bugs completely breaking jenkins, only in a couple of weeks :-(
Re: Very long load time for main dashboard since 1.486
Yes, same issue. I have load times of at least 3 minutes for the main dashboard. It occurs since that "lazy loading" functionality was introduced, which makes the whole lazy loading thing quite pointless. Maybe it was intended to have faster startup times, but as we're loading the main dashboard after startup, so now it still takes long to startup. And what's worse: it now also takes 3-5 minutes just to return from a job to the main dashboard, or to refresh a dashboard. Which makes jenkins unresponsive and even rather unusable. PS: no I have no nest view plugin.
Re: Jenkins 1.485 bug - not displaying statuses and history
Same issue here : everything job is grayed out, and no build history get loads, no build results visible, etc... Since that "lazy loading" feature 1.485 jenkins just can't read job and build data correctly anymore and messes up totally. One advice : restore the previous jenkins version. If you revert to 1.484 (if you use Maven, don't forget to revert the Maven plugin as well), everything will work nicely again. No historical build results will be lost. Jenkins 1.485 is seriously broken and completely *unusable* !
