[Tails-dev] Build failed in Jenkins: build_Tails_ISO_experim…

このメッセージを削除

このメッセージに返信
著者: tails-sysadmins
日付:  
To: tails-dev
古いトピック: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #1521
新しいトピック: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #1523
題目: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #1522
See <https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/1522/>

------------------------------------------
Started by an SCM change
Building remotely on isobuilder2 in workspace <https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/ws/>

Deleting project workspace... done

Wiping out workspace first.
Cloning the remote Git repository
Cloning repository gitolite@???:tails
> git init <https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/ws/> # timeout=10

Fetching upstream changes from gitolite@???:tails
> git --version # timeout=10
> git fetch --tags --progress gitolite@???:tails +refs/heads/*:refs/remotes/origin/*

ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --tags --progress gitolite@???:tails +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
bc:60:41:ce:96:ad:c0:68:c5:33:87:ba:cd:9f:a5:9c.
Please contact your system administrator.
Add correct host key in /var/lib/jenkins/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /var/lib/jenkins/.ssh/known_hosts:1
RSA host key for puppet-git.lizard has changed and you have requested strict checking.
Host key verification failed.
fatal: The remote end hung up unexpectedly


    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1225)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:87)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:282)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:438)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
    at hudson.remoting.UserRequest.perform(UserRequest.java:118)
    at hudson.remoting.UserRequest.perform(UserRequest.java:48)
    at hudson.remoting.Request$2.run(Request.java:328)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at hudson.remoting.Engine$1$1.run(Engine.java:63)
    at java.lang.Thread.run(Thread.java:701)
ERROR: null